HP Oneview Deployment and Management Guide v1

Technical Whitepaper
HP OneView Deployment and

Management Guide
How to Deploy and Manage OneView, Version 1.05
Table of contents
Introduction .................................................................................................................................................................................... 3
HP OneView 1.05 Features ..................................................................................................................................................... 3
HP OneView 1.0 Features ........................................................................................................................................................ 3
Browser Requirements ............................................................................................................................................................ 4
Supported Hardware ................................................................................................................................................................ 4
HP OneView User Interface Overview ................................................................................................................................... 6
HP OneView Virtual Connect Management Architecture Overview ................................................................................ 6
Deploying Your Appliance ............................................................................................................................................................ 6
Section D1: First Time Setup .................................................................................................................................................. 7
Section D2: Firmware Repository ........................................................................................................................................ 12
Section D3: Licensing OneView ............................................................................................................................................ 13
Section D4: Network Configuration ..................................................................................................................................... 14
Section D5: Import Enclosure ............................................................................................................................................... 28
Section D6: Add ProLiant DL Gen8 Server ......................................................................................................................... 40
Section D7: Upgrade Infrastructure Firmware .................................................................................................................. 42
Section D8: Creating Server Profiles ................................................................................................................................... 46
Section D9: Environmental Management .......................................................................................................................... 55
Section D10: Securing the Appliance with Active Directory/LDAP................................................................................ 63
Maintaining Your Environment ................................................................................................................................................. 70
Section M1: Alerts and Monitoring ...................................................................................................................................... 70
Section M2: Add New Networks and Edit Server Profile ................................................................................................ 75
Section M3: Adding a New Enclosure .................................................................................................................................. 77
Section M4: Adding a Ethernet Network ............................................................................................................................ 79
Section M5: Adding a Fibre Channel Network ................................................................................................................... 81
Section M6: Adding an Ethernet Uplink to a Logical Interconnect ................................................................................ 82
Section M7: Adding a Fibre Channel Uplink ....................................................................................................................... 84
Section M8: Removing Networks from a Server Profile ................................................................................................. 88
Click here to verify the latest version of this document

Technical white paper | HP OneView Deployment and Management Guide
Section M9: Creating New Users .......................................................................................................................................... 89

Section M10: Deleting Existing Users ................................................................................................................................. 90
Section M11: Changing User Permissions ......................................................................................................................... 91
Section M12: Adding a New Blade to an Enclosure and Discovering New Server Hardware Types ..................... 92
Section M13: Adding New Racks Based on Location Discovery Services ................................................................... 93
Section M14: Adding Enclosures to Racks without Location Discovery Services ..................................................... 93
Section M15: Adding Rack Servers (DL’s) to Racks without Location Discovery Services ...................................... 94
Section M17: Adding a Service Pack for ProLiant (SPP) Bundle .................................................................................... 95
Section M18: Updating the Firmware Baseline for Existing Servers with Profiles Assigned .................................. 96
Section M19: Managing Multiple Firmware Images in the Same Enclosure............................................................... 98
Section M20: Modifying Virtual ID Pools ..........................................................................................................................103
Section M21: REST API .........................................................................................................................................................105
Section M22: Creating a Support Dump ...........................................................................................................................108
Additional Resources ................................................................................................................................................................110
2
Introduction
Welcome to the Quick Start, Deployment and Management Guide for HP

OneView. HP OneView provides a simple, consumer-inspired user experience
that dramatically accelerates everyday tasks. By changing the focus from ‘how
devices are managed’ to ‘how people work,’ HP OneView delivers a software-
defined management platform that is extensible and easy to use.
This document will guide administrators through the setup process, and how to
manage the next generation of Converged Infrastructure with HP OneView. The
flow chart below outlines these steps.
First Time Configure Discover Upgrade Server Environment Appliance

Setup Networking Hardware Firmware Profiles Management Security
• Change • Create Ethernet • Import C7000 • Examine Installed• Server Profile • Configure Active
Administrator Networks Enclosure Firmware Templates Directory or
password • Create Single-hop• Import ProLiant • Manage Virtual • Managing Server OpenLDAP
• Accept EULA FCoE Fabrics DL Gen8 Connect Firmware Profiles • Configure
• Remote Support • (Optional) HP Directory Groups
Opt-in 3PAR StorServe
• Configure Direct Attach
Appliance IP • Network Sets
Settings • Logical
Interconnect
Groups
• Enclosure Groups
HP OneView 1.05 Features

The following list outlines what is introduced in the release:
Table 1. HP OneView 1.05 Features
VC-Style Active/Active Configure Active/Active Uplink Sets for increased bandwidth utilization.
Networking
Server Profile Connection Online Update existing Network Connections within the Server Profile while the server is still powered
Updates on, both Network/Network Set assignment and bandwidth allocation.
Local SmartArray Configuration Define the embedded SmartArray logical disk configuration as part of your Server Profile.
HP OneView 1.0 Features

The following list outlines what was introduced in the release:
Table 2. HP OneView 1.0 Features
Virtual Appliance Rapidly deploy appliance OVF with single setup screen
Firmware Updates On appliance repository, search, and management network only. No need to inventory host OS.
3
Enclosure Groups Configure a new enclosure just like the last one in seconds
Logical Interconnect Groups VC module configuration with uplinks
Server Hardware Types Inventory of your standardized hardware configurations
Enhanced Server Profiles VC classic connectivity plus FW, BIOS, and boot config
Network Sets Centralized VLAN configuration for Server Profile Network Connections
Enabling 3Par Flat SAN Dramatically reduce traditional FC SAN infrastructure with VC FlexFabric modules
Onboard Administrator and iLO Reduce the number of steps to manage the Management Processors.
Single Sign-On and Alert
Management
Manage DL Servers Add DL ProLiant rack mount servers for inventory and health
Alert and Monitor Systems in the iLO 4 traps automatically configured on import, no OS agents required
Datacenter
Environmental Management Model and analyze power, cooling and location of your HP IT equipment
Secure Appliance Integrate the appliance into your Active Directory or OpenLDAP infrastructure
Visualizing the Datacenter Visualize your data center’s layout and rack power consumption
Map View Understand how things are connected from the data center down to the device
Smart Search Quickly find the information you are looking for. Need to locate an HP OneView Managed
Address? Type it in the Search Field to find the Server Profile it’s assigned to.
Browser Requirements
Please note that the following web browsers are a minimum requirement:
Table 2. Supported Browsers
Internet Explorer 9 and 10
Mozilla Firefox 14 or newer
Google Chrome 21 or newer
Safari Unsupported
Opera Unsupported
WARNING
Internet Explorer 8 is not supported. Please use another supported browser.
Supported Hardware1
Supported Enclosures
• All C7000 BladeSystem Enclosures
1
Please review the HP OneView Support Matrix on http://www.hp.com/go/oneview/docs
4
Supported Servers
• All HP ProLiant Gen8 BL-family of servers
• All HP ProLiant Gen8 DL-family of servers
• BL460/465 G7
• BL490 G7
• BL685 G7
• BL680 G7
Supported IO Adapters
• All HP Flex-10 and FlexFabric 10Gb adapters
• BladeSystem HBA’s are allowed, but will be unmanaged and must be connected to non-Virtual Connect FC modules.
Supported Interconnects
• HP Virtual Connect FlexFabric 10Gb/24-Port Module
• HP Virtual Connect Flex-10 10Gb Ethernet Module
• HP Virtual Connect Flex-10/10D Ethernet Module
Hardware Firmware Minimum Requirements

Table 3 shows the minimum firmware requirements needed to successfully import an enclosure. Firmware will be updated
via the appliance to the required versions later in this document.
Table 3. Minimum Firmware Requirements
Onboard Administrator 3.00 or newer
iLO4 1.01 or newer
iLO3 1.20 or newer
Virtual Connect 3.15 or newer
Table 4. Post Import Firmware Minimum Version
Onboard Administrator 4.01
iLO4 1.30
iLO3 1.61
Virtual Connect 4.10
Note
The Appliance Virtual Machine should not be deployed on a hypervisor within the same enclosure it will manage. Please use
an externally available hypervisor host.
Table 5 shows the HP OneView 1.0 and 1.05 Configuration Maximums.
Table 5. Supported Maximums
Total Servers 640
Servers per Enclosure 16
Total Enclosures 40
5
Total Interconnects 160
Total Enclosure Groups 40
Total Server Profiles 740
Assigned Server Profiles 640
Total Unassigned Server Profiles 100
HP OneView User Interface Overview

The entirely new HP OneView user experience is significantly improved from previous generations of HP Management
software (e.g. HP System Insight Control.) The HP OneView user interface is built using modern web programming
languages, HTML5 and CSS3. Below is an example of what the User Interface looks like (UI.)
Figure 1. HP OneView User Interface
Your User Account Online Help
Top Level Menu
Universal Search
Sub-Menu
Map View
Activity Details
Object Selection/Filter
Details Pane Activity Window
HP OneView Virtual Connect Management Architecture Overview

HP OneView’s Virtual Connect management architecture is different from that of Virtual Connect Manager (VCM) or even
Virtual Connect Enterprise Manager (VCEM.) While VCM provided a consolidated management view, it is limited to a
maximum of 4 Enclosures within a Multi-Stack Enclosure (MES) Domain configuration. This limits management scalability.
VCEM represents a Manager-of-Managers architecture, where VCM is put into a locked state, and VCEM controls the
configuration. When an enclosure containing Virtual Connect modules is claimed and managed by OneView, Virtual Connect
Manager is no longer in use. It cannot be used for any level of management, as HP OneView is the manager.
Deploying Your Appliance

This segment will guide you through deploying your HP OneView appliance. It will cover the First Time Setup, examining the
Service Pack for ProLiant image pre-loaded in the firmware repository, create your Ethernet and FCoE Networks, associate
the networks to Logical Interconnect Groups, and begin importing devices.
6
Section D1: First Time Setup

• Change
Administrator
password
• Accept EULA
• Remote Support
Opt-in
• Configure Appliance
IP Settings
Completing the HP OneView appliance First Time Setup is designed to be simple and straightforward. By default, the
management interface is configured for IPv4DHCP. If DHCP is not available on the management network you can access the
Kiosk Browser within the VM console from the vSphere Client to complete the initial setup. If DHCP is available, you can
configure the appliance with a browser remotely to complete the First Time Setup. The First Time Setup consists of
Accepting a License Agreement, HP Remote Support Access for remote troubleshooting, changing the default Administrator
account password and configuring IP information.
Prior to continuing with this document, please make sure you have completed the following:
Table 6. Installation Checklist
Task Completed? (Y|N)
Have a supported vSphere 52 host for appliance
Have Static IP Address, or DHCP Static Reservation
Have DNS A and PTR Records created
Figure 2. Obtain the Virtual Machine IP Address
As shown in Figure 2., obtain the IP Address of the virtual machine, and open a supported Web Browser to the noted IP
Address to complete the First Time Setup. If DHCP is not available, then you can continue the following steps using the
embedded Kiosk Browser, by launching the VMware VM Remote Console.
2
Please review the HP OneView Support Matrix on http://www.hp.com/go/oneview/docs for the officially supported hypervisors.
7
Figure 3. Appliance Startup and Initialization Screen using the vSphere Client
Figure 4. License Agreement
8
Figure 5. HP Support Access Opt-In
The HP Support Access Opt-In, as shown in Figure 5, is used for the HP GCC remote access when the appliance is in an
unhealthy state, and core services cannot start. By opting out, this also disables the ability to reset the appliance
Administrator account password if ever lost.
Table 7. Default Credentials
Username Password
Administrator admin
Figure 6. Login Page
9
Figure 7. Change Administrator Password
After providing the new Administrators password, you will be prompted for Appliance Networking configuration. You will
need the following:
• Appliance Hostname (e.g. hponeview.example.com)
– If you specify an FQDN, verify valid A and PTR records exist. The appliance will perform an nslookup of the FQDN and IP
address and report an appliance warning if neither are available.
• IPv4 Address (DHCP or Static can be used).
– DHCP is only supported when Static Reservations are used.
• Default Gateway
• (OPTIONAL) DNS Servers
• (OPTIONAL) IPv6
• SNTP
10
Figure 8. Configure Appliance Networking
After clicking OK, the appliance will configure those parameters. If you selected Static for the IP Address Assignment, you
should be redirected to the new IP address. Please accept the certificate security warnings during the redirection, as a new
SSL certificate is generated from the FQDN.
Caution
If the Management IP Address needs to be changed after completing the First Time Setup, change it prior to adding
enclosures. Otherwise enclosures under management will lose the connection to the management appliance. It is advised
to re-deploy the appliance, and re-add the enclosure(s).
11
Section D2: Firmware Repository

The HP OneView appliance ships with a default SPP that contains the necessary firmware to successfully import and
manage an enclosure. It is unnecessary to upload an SPP into the appliance, unless a custom baseline (created by HPSUM6)
is required.
1. Select the Top Level Menu, and navigate to Firmware Bundles in the console
2. Examine the default SPP Baseline
3. If you wish to upload an alternate SPP Bundle, clicking the +Add Firmware Bundle button will display the Add Firmware
Bundle screen. Click on the Choose File button, and select the SPP ISO to upload. Once selected, click the Start Upload
button. You can also drag-and drop firmware bundles (SPPs) within Windows environments. You can navigate away
from the Firmware Bundle screen to other areas within the UI, as the upload process is a background process within
the browser.
12
4. The SPP upload will being. You can click the blue Close button in the lower right, as that will only close the dialog box
and not cancel the upload.
Note
Do not close the browser window until the Firmware Upload task has completed. You can click on the Close button in
the Add Firmware Bundle dialog as the upload is a background thread within the web application.
Section D3: Licensing OneView

HP OneView licensing is designed to be simplified, with the license typically embedded within the iLO or Onboard
Administrator when ordered with Factory Express, CTO or BTO. Please refer to the HP OneView Quickspecs for all possible
licensing options.
HP OneView also has a built-in 60-day evaluation license. During this evaluation period, HP OneView will not enable iLO
Advanced features or functionality. The ILO Advanced license (trial or retail) is also required for server and enclosure power
and performance monitoring.
If you have received a license key, use the appliance Settings menu to add licenses to the internal pool. The following steps
outline that process.
1. Select the Top Level Menu, and navigate to Settings in the console
13
2. Open the Actions menu, and select Add License.
3. Paste in your license key in the dialog box and click Add to apply the license.
4. On the Licenses page, verify that your license count has increased.
Section D4: Network Configuration
Power,
First Time Configure Discover Upgrade Server
Cooling
Setup Networking Hardware Firmware Profiles
Management
• Create Ethernet
Networks
• Create Single-hop
FCoE Fabrics
• (Optional) HP 3PAR
StorServe Direct
Attach
• Network Sets
• Logical Interconnect
Groups
• Enclosure Groups
In this section, you will create Networks, Network Sets, Logical Interconnect Groups and Enclosure Groups.
Networks are constructs within the appliance that define a particular L2 network or FCoE/FC Fabric. A Network will be an
object you can assign to Server Profiles, Network Sets, and Logical Uplink Sets. With the HP OneView 1.0 release, te VLAN ID
14
must be unique within the appliance, as the version only support Active/Standby Virtual Connect networking configuration.
The HP OneView 1.05 release introduced Virtual Connect Active/Active networking, so each Ethernet Network does not
require unique VLAN IDs. Similar to Virtual Connect provisioning all Ethernet Networks to all Ethernet modules within a
Virtual Connect Domain, HP OneView provisions all defined Ethernet Networks to all managed Ethernet-capable modules.
Network Sets are aggregated networking objects that contain Networks. The Network Set will be an object you can assign to
Network Connections within Server Profiles to greatly simplify multiple network management. For instance, if you have a
number of standard Networks required for Virtual Machine connectivity, which is different for physical servers, you can
create different Network Sets for each host connectivity model. Network Sets replace the Multiple Networks Virtual Connect
concept, and becomes the only way to trunk multiple networks to a Network Connection.
Logical Interconnect Groups are similar to Virtual Connect Enterprise Manager Domain Groups, which define what modules
are located within the enclosure and the module configurations like IGMP Snooping, Loop Protection, Multicast Filtering, etc.
Uplink Sets define uplink connectivity for Ethernet, FCoE and FC Networks, and are members of a Logical Interconnect
Groups. The Logical Interconnect Group is then assigned to an Enclosure Groups to complete the Enclosure configuration
policy. A Logical Interconnect is patterned after the Logical Interconnect Groups and is defined automatically once an
Enclosure is added to the HP OneView console by associating it to an Enclosure Group.
Uplink Sets are synonymous with the Shared Uplink Set within Virtual Connect, in that it defines the uplink connectivity for
selected networks. An Uplink Set can either be an Ethernet or Fibre Channel type, but not both. With the HP OneView 1.0
release, Uplink Sets could only be configured in an Active/Standby design, and must connect to an 802.1q configured
adjacent switch port(s). The HP OneView 1.05 release introduced Virtual Connect Active/Acitve design. Any defined
Networks not associated with an Uplink Set become Internal Ethernet Networks to the Logical Interconnect, and are reported
within the Logical Interconnect.
An HP OneView Domain is a new concept to the Converged Infrastructure management framework. While you cannot create
additional HP OneView Domains, the appliance itself is a single Domain construct. An HP OneView Domain consists of one or
more Logical Interconnect Groups, Uplink Sets, Networks and help to define how Server Profiles consume these resources.
When defining a Network, it will be available within the HP OneView Domain for consumption by either a Logical Interconnect
Groups, Logical Uplink Set, Logical Interconnect (for one-off configuration requirements) or Server Profiles (for Internal Only
networks.)
Prior to continuing with this document, please make sure you have completed the following:
Table 8. HP OneView Network Configuration Checklist
Collect the Virtual Connect Module Types
Note the uplink ports connected to the upstream switches
Document necessary VLAN IDs and names
Document necessary Fibre Channel Fabrics
Creating Ethernet Networks

1. Select the Top Level Menu, and select Networks.
15
2. Once on the Networks screen, click the +Create Network button on the far left.
3. In the new window, provide the Name, select Ethernet as the Type, provide the VLAN ID, and bandwidth settings. Smart
Link will automatically be selected by default. The Name is not case-sensitive, can contain spaces and special
characters. Selecting Private Network will mimic PVLAN behavior in that all assigned Network Connections will all be in
an isolated network. The Purpose dropdown selection is used by the HP Insight Control for vCenter Plugin3.
Note
Virtual Connect Active/Active Networking is now supported in version 1.05.
4. Click the Create button to create the new Ethernet Network and close the Create Network dialog box. You can also
select the Create+ button to continue creating more Networks – e.g. Create the B-Side Ethernet Network.
Creating FCoE SAN Fabrics
HP OneView supports single-hop FCoE Fabrics in the 1.0 /1.05 release with either traditional Fibre Channel Fabric Attach, or
Virtual Connect FlatSAN with HP 3Par StoreServe Direct Attach. Please choose the appropriate following scenario to create
either a Fabric Attach or 3Par Direct Attach Fabric.
3
http://h30507.www3.hp.com/t5/Converged-Infrastructure/Finally-an-integrated-tool-based-on-how-I-work/ba-p/154413#.Ux1MmyyUPX4
16
Fabric Attached Network

1. From the Top Level Menu, select Networks, then select the +Create Networks button.
2. In the new window, provide the Name, select Fibre Channel as the Network Type, select Fabric Attach as the Fabric Type,
and modify Bandwidth allocation, Uplink Speed, Login Redistribution as needed.
Note
The Fabric Attach Fabric Type is used for traditional Fibre Channel Fabric connectivity, which requires NPIV-capable
upstream FC switches.
Note
By selecting the Fabric Attach Fabric Type, you can assign any of the available X1-X4 ports on a Virtual Connect
FlexFabric module to an FC switch.
select the Create+ button to continue creating more Networks.
HP 3Par StoreServe Direct Attach (Optional)
The HP 3Par StoreServe FlatSAN feature extends Virtual Connects “Wire-Once” management to the FC fabric by reducing the
complexity, and cost of expensive FC switches. This feature is only supported with HP 3Par StoreServe arrays, and not with
other HP or 3rd party storage arrays.
1. From the Top Level Menu, select Networks, then select the +Create Networks button.
17
2. In the new window, provide the Name, select Fibre Channel as the Network Type, select Direct Attach as the Fabric Type,
and modify Bandwidth allocation and Uplink Speed.
Note
By selecting the Direct Attach Fabric Type, you can assign any of the available X1-X4 ports on a Virtual Connect
FlexFabric module to an HP 3Par StoreServe array.
3. Click the Create button to create the new Direct Attach Network and close the Create Network dialog box. You can also
Creating Network Sets
1. Select the Top Level Menu, and choose Network Sets.
18
2. Once on the Network Sets screen, click the +Create Network Set button on the far left.
3. On the Create Network Sets screen, provide a name, then click the Add Networks button to select the networks to add.
4. You can search for a Networks or multiple Networks, or either click SHIFT/CTRL+Left Mouse Click to select which will
either select all in section, or multi-select the networks to add. The following example shows how to find the “A-Side”
19
Ethernet Networks, and create the “A-Side” Network Set.
5. After clicking Add, you can select the specific network that will be the Native VLAN, or the default untagged network for
the Servers Network Connection. This is typically used for PXE traffic.
20
6. If you are creating an Active/Active network design, repeat the prior steps to create the “B-Side” Network Set.
Create Logical Interconnect Group

1. Select the Top Level Menu, and choose Logical Interconnect Group (LIG).
2. Once on the LIG screen, select the +Create Logical Interconnect Group button.
3. Provide a name to best describe the template. Use terms like Production or Dev to help describe the Logical
Interconnect Group.
4. Click the Add interconnect button to add modules to Bays 1 and 2. Select the correct Virtual Connect Modules, either VC
Flex-10, VC Flex-10/10D or VC FlexFabric. When clicking the Add Module button next to the peer bay, the UI will
21
automatically select the correct module.
Creating Uplink Sets

1. Click the Add uplink set button.
2. On this window, we will create an Ethernet Type Uplink set representing an Active/Active configuration. Provide a Name,
select Ethernet as the Type.
3. Click the Add networks button to select the networks to add. By not selecting a Network or multiple Networks, they will
be Internal Ethernet Networks within the Logical Interconnect that is applied to each enclosure from the Logical
Interconnect Group. A search field is provided to quickly locate a specific Network or multiple Networks. After
searching you can either Left Click to select a single network or SHIFT/CTRL+Left Mouse Click to multi-select networks.
Once all of your networks are selected, click the Add button, or click the Add+ button to continue to add more networks
22
by searching.
4. Make sure to mark the appropriate network as Native if the VLAN on the upstream switch is also the Native or Default
VLAN.
5. Click the Add ports button to add uplink ports.

6. Select at least one port from each Ethernet Module. To quickly add multiple Uplink Ports, first search for a common
port (e.g. X5), select them, click the Add+ button, then change the search to another port (e.g. X6) and click the Add
23
button.
7. After you have added the Uplink Ports to your Uplink Set, click the Create button. Select the Create+ button if you wish
to define an additional Uplink Set – e.g. the B-Side Uplink Set. Otherwise, select the Create button.
8. Continue to the next section to create Fibre Channel Uplink Sets. Otherwise, click the General dropdown list and select
Switch Settings, or scroll the window to the bottom to modify Ethernet Module parameters like IGMP Snooping, Loop
Protection, Fast MAC Cache Failover, SNMP settings, etc.
24
Creating Fibre Channel Uplink Sets (Optional)

1. Click the Add uplink set button to add SAN Fabrics.
2. Select Fibre Channel as the Type, provide a Name, select the SAN Fabric Name, Interconnect, and then select which
ports are to be linked.
Note
The Interconnect field will display the Interconnect Module by its Bay ID.
25
3. Click the Create+ button.

4. Repeat to create the redundant SAN Fabric. Notice that the other Fabric is filtered from view.
5. Click the Create button.
6. If you wish to create another Uplink set, repeat the above steps, or click the Create button.
Reviewing Logical Interconnect Group Configuration

1. After creating the Logical Interconnect Group, select the Sub-Menu and choose General
26
2. Scroll down to bring the Logical Interconnect Group section into view, and mouse over of the Uplink sets. Examine the
relationship of the Uplink set to the physical modules and their uplink ports.
3. Scroll down to bring the Logical Uplinks section into view. Examine the Logical Uplinks and their relationship to the
assigned Networks.
Create Enclosure Group

An Enclosure Group is a centralized configuration policy, similar to that of the Logical Interconnect Group, in which all
associated Enclosures retrieve their configuration from. With the HP OneView 1.0/1.05 version, the Enclosure Group will
only define the Logical Interconnect Group association, and contain embedded, un-configurable management settings.
These management settings are SNMP, NTP and the HP SIM Single-Sign-On (SSO) Certificate for agentless and touchless
management configuration.
1. Select the Top Level Menu, and select Enclosure Groups.
27
2. Click on the Create Enclosure Group button
3. In the Create Enclosure Group screen, provide a Name, and select the appropriate Logical Interconnect Group you
created earlier. Notice that if only a single Logical Interconnect Group exists, it will be selected by default.
4. Click the Create button to create the Enclosure Group, or Create+ to create the Enclosure Group and additional Enclosure
Groups.
Section D5: Import Enclosure
• Import C7000
Enclosure
In this section, you will go through the process on how to import an enclosure into the HP OneView console. In order to
successfully import an enclosure, the Onboard Administrator must be configured. At a minimum, both the Primary and
Secondary OA must have a valid IP Address, Enclosure Bay IP Addressing or external DHCP Server supplying IP leases, and a
valid Administrator-role account. During the Enclosure Import process, HP OneView will automatically configure SNMP, NTP
and the HP SIM Single-Sign-On Certificate with the HP OneView appliance IP Address and public SSL Certificate. The
28
Enclosure Import process will also discover any device in the enclosure’s Device Bays, and attempt to configure the
supported iLO ’s for management (SNMP, NTP, HP SIM SSO Certificate, create a special user account _HPOneViewAdmin) and
license the iLO ‘s and servers based on the License Intent setting in the Add Enclosure screen.
Table 9. Enclosure Import Checklist
Documented Onboard Administrator IP Address or FQDN
Documented Onboard Administrator administrator

credentials
Configured Onboard Administrator settings (EBIPA, Power

Redundancy, etc.)
Warning
Release 1.0 and 1.05 do not support importing an existing Virtual Connect Domain. If one is present, it will be deleted if you
force the addition of the enclosure into the appliance.
1. Navigate to Enclosures in the console.
2. Click the Add Enclosure button.
3. Import your first enclosure, select the Enclosure Group, define the license policy, and specify the Firmware Baseline to
apply. Selecting the Add or Add+ button, the enclosure will be discovered, and the OA firmware will be updated to the
29
version within the SPP.
4. HP OneView provides audit tracking within the appliace. By clicking the gear in the lower left corner, HP OneView
shows you to what you have changed in the dialog screens.
5. Once the enclosure information has been verified, the appliance will begin its discovery process.
30
During this time, the appliance will validate if the OA firmware meets the minimum requirement.
31
Clicking on the Details link will take you to the Activity view of the enclosure, were you can examine the task and
subtask details.
If the firmware was out of date, the Activity window would display the sub-tasks generated. Below is a sample
screenshot.
32
6. After the Add Enclosure task has completed, the Enclosure State should read Configured.
7. After adding the first enclosure, there might be a Warning status message, indicating the appliance encountered
problems with the servers during discovery.
33
Clicking on the Details link will take you to the Activity page of the enclosure. In the following example, HP OneView is
reporting no licenses are available. Instead, the 60-day “trial” license will be applied.
8. Repeat the above steps to add more enclosures.

Examine Imported Resources
After you have successfully imported the enclosure, you will want to verify all the resources in the enclosure have been
imported.
Physical and Logical Interconnects
1. Select the Top Level Menu, and choose Interconnects
2. Interconnects are the physical Virtual Connect Modules. If the Virtual Connect modules meet the minimum required
version, they should be in a Configured State. If the firmware version didn’t meet the minimum management
requirements, the State of the module would be Unmanaged.
34
3. Select the Top Level Menu, and choose Logical Interconnects
4. The Logical Interconnect view is how the VC Modules within the Enclosure are configured based on the Logical
Interconnect Group you defined earlier.
Server Hardware
1. Select the Top Level Menu, and choose Server Hardware.
35
2. In this section, you will see the discovered servers listed in the left panel. Selecting a specific server will provide you
with the details.
Server Hardware Types

Server Hardware Types are the unique server hardware configurations discovered during the addition of imported
enclosures. Their role within the HP OneView is to define the hardware configuration of each server type, which can include
the adapter and its location, BIOS settings and even firmware. With HP OneView knowing the server hardware and its
adapter configuration, it will allow the administrator to place Network Connections on the specific physical port when
creating Server Profiles. The Server Hardware Type is automatically created when an Enclosure or a Rack Mount server is
added.
1. Select the Top Level Menu, and choose Server Hardware Types.
1. Examine the different Hardware Types.
36
2. You can edit a Server Hardware Type, but only to rename it or add a description.
Examine Relationships
Let’s examine the HP OneView mapping and relationship capabilities. We’ll look at the Enclosure, blade and Networks.
1. Navigate to Enclosures in the console.
2. To access the Map View, you can click on the Map button, or select Related from the sub-menu.
37
3. Within the Map view, hover over objects to see how the relationships are built. In the following example, you can see
the relationship built when you mouse-over the Enc1 Enclosure. Clicking on an object will navigate you to that objects
Map View.
38
4. Mouse over and locate one of your blade servers. Notice the relationship between the Enclosure, Server Hardware
Type, and Interconnect Bays. Click on the Server object.
5. After selecting one of your servers, notice the Map View now displays different information. Hover over the Server
Hardware and notice the relationship shown.
6. Lastly, we will examine Network relationships. As we don’t have a Server Profile assigned yet, you cannot examine the
Network relationship to the server. So you need to navigate to the Networks section of the UI. Select the Top Level
Menu, the choose Networks.
39
7. Select an available Network, and click the Map View button. Mouse over the network, and examine the relationship tree
that is built.
Section D6: Add ProLiant DL Gen8 Server

• Import ProLiant DL
Gen8
HP OneView supports adding a ProLiant Gen8 DL for health and alert management only. In this section you will add a DL
Gen8 server by adding the iLO IP Address or FQDN.
1. Select the Top Level Menu, then choose Server Hardware.
40
2. In the Server Hardware screen, click the +Add Server Hardware button.
3. In the Add Server Hardware screen, add the first DL380 Gen8 server’s iLO FQDN or IP Address, along with Administrator
credentials. Click the Add button to add the DL server, or select the Add+ button to continue adding DL Gen8 servers.
41
4. After clicking the Add button, HP OneView will being to discover the server, and configure the iLO for management.
5. Once the server is added, you can power it on and launch the Remote Console from the Actions menu.
6. The server is now configured for element management by HP OneView.

Section D7: Upgrade Infrastructure Firmware
• Examine installed
firmware
• Manage Virtual
Connect firmware
In this exercise, you will examine the firmware status of the imported enclosures and servers.
Examine Infrastructure Firmware
The first place to start is with the Enclosure. There is a Firmware sub-menu view that you can switch to, which will report
the firmware installed. If a Firmware Baseline was attached during the Enclosure import process, it will also report the
available version in the Firmware Baseline.
42
1. Navigate to Enclosures from the Top-level Menu. Select Firmware in the submenu.
2. Examine what is installed versus what is available in the Firmware Baseline.
Managing Virtual Connect Firmware

HP OneView provides the ability to manage Virtual Connect firmware from multiple locations; at the Logical Interconnect or
Enclosure level. Managing Virtual Connect firmware at the Logical Interconnect would be used for those times where only VC
firmware requiring updating.
1. Select Logical Interconnects from the Top Level Menu.
43
2. In the Logical Interconnects view, validate the [ENC-Name]-LI Logical Interconnect is selected, then the Actions menu
select Update Firmware.
3. On the Update Firmware on [ENC-NAME]-LI window, select the Firmware Baseline, and select Update Firmware (stage +
activate) action. The other two options are for staging firmware to initiate a manual activation of the Virtual Connect
firmware. The second option Stage firmware for later activation is used to deploy and stage the firmware for later
manual activation by the admin. If firmware has been previously staged, the final option would become active.
Note
HP OneView does not offer the ability to modify Activation order, and each module is Activated independently and at the
same time, which will cause a network outage. To control potential outages, consider staging and manual activation of
Virtual Connect firmware.
44
4. Clicking OK will begin the firmware update process.
However, if you want to examine the individual update process for each Virtual Connect module, click the Details link in
the Activity bar.
45
5. Once the firmware update has completed, examine the Firmware section, and see that it should show the Firmware
Baseline assigned, the Installed and Baseline versions.
Section D8: Creating Server Profiles

• Server Profile
Templates
• Creating and
Assiging Server
Profiles
Server Profiles are managed objects that specify supported settings for the selected Server Hardware Type (e.g. Hardware
Platform, Adapter Layout/Network Connections, BIOS Settings) and Enclosure Group (e.g. Networks based on Logical
Interconnect), and can be left Unassigned for use as a Template. A Firmware Baseline (Policy) is set within the Server Profile,
which will automatically update the firmware prior to assigning and configuring the Server Profile to the Device Bay it’s
assigned.
In this chapter, you will first create a Server Profile to be used as a Template that defines specific elements. The Server
Profile Template will then be copied and assigned to a Server Hardware Device.
Create Server Profile for Template Use
Creating a Server Profile Template is simply defining the Server Hardware as Unassigned. Specify the Server Hardware Type
and Enclosure Group the Server Profile will be bound to, and then all other profile settings.
1. Select the main menu option in the upper left, and choose Server Profiles.
46
2. Once on the Server Profiles screen, select the +Create Profile button
3. Provide a Name and Description for the Server Profile. Select Unassigned for the Server Hardware, and the Server
Hardware Type and Enclosure Group will be accessible. Attach a Firmware Baseline to the Server Profile. When
selecting either the Server Hardware Type or Enclosure Group will filter the assignable Server Hardware section.
Note
HP OneView does not currently support Server Profile inheritance. E.g. 1:Many Profile Assignment.
4. Add the needed Network Connections by clicking the Add Connection button, specify an Ethernet Device Type and either
assign an Ethernet Network, or Ethernet Network Set to the Connection. Click the Add+ button to continue adding
47
Network Connections to the Server Profile.
Note
HP OneView 1.05 support Virtual Connect Active/Active Network Designs.
Note
You can specify which FlexNIC to assign the Network Connection to, or leave it at the default of Auto. Auto will apply
the same Network Connection to Adapter mapping Virtual Connect does today. Do know that you cannot create a
FlexNIC B, C or D without first creating FlexNIC A.
Note
The Use user-specified IDs is for those customers that wish to provide their own MAC or WWN address for that
connection.
5. (Optional) Adding Fibre Channel Networks is a similar operation as an Ethernet Deviec Type. FlexNIC B is reserved for FC
Connections when FC Connection Types are added to the Server Profile. When choosing the FlexNIC, you can leave the
default Auto. You can force the FlexNIC assignment, but the list will be filtered based on the connection location to the
Interconnect Bay the FC Network is assigned to.
48
A. (Optional) If you wish to configure FC Boot From SAN (BFS), change the Boot setting from Not Bootable to either
Primary or Secondary. You will need to provide the Target WWN and Host LUN ID in the respective fields.
6. HP OneView 1.05 introduced the ability to manage the Local Embedded Smart Array controller. You can enable local
storage management by selecting it.
If you enable the Manage Local Storage feature, a warning dialog will be displayed mentioning what the Initialize local
49
storage option does.
7. Modify the Boot Order if necessary.
Warning
Disabling Boot Order in the Server Profile will also disable PXE and FC BfS configuration options.
8. Modify the following, or customize your own BIOS Settings

A. Add a Custom Post Message under the Server Asset Text section. E.g. “HP ONEVIEW ROCKS!”
B. Change the HP Power Regulator setting to HP Static High Performance under the Power Management Options
section.
Notice when you change the HP Power Regulator from the default to HP Static High Performance, the HP Power
Profile, Intel QPI Link Power Management, Minimum Processor Idle Power Core State, and other related BIOS
settings change.
Note
50
If the server hardware only contains a single CPU, you will need to change the HP Power Profile setting to Custom, and
then change Intel QPI Link Power Management to its default value, otherwise the Server Profile will fail to apply. This
BIOS setting is only available on systems that contain multiple CPUs.
9. Leave the Advanced section as default, which would be Virtual Managed Addresses.
10. Click Create.

11. Now that the Server Profile Template has been created, you can now copy it. Select Copy from the Actions menu.
51
12. In the Copy Profile screen, provide a Name, specify the Server Hardware that you will assign this Server Profile to, then
click the Create button.
Note
The Server Hardware list will be filtered based on the Server Hardware Type and Enclosure Group that the Server Profile
Template was configured for. You cannot change them in the Copy Profile screen.
13. During the creation of the Server Profile, it will be assigned to the selected Server Hardware bay, and the firmware
update process will begin.
52
14. Either select Server Hardware from the top level menu, or the Server Hardware link in the Server Profile to be taken
directly to the Server Hardware view.
15. From here, you can launch the iLO Remote Console, select the Actions menu, and then Remote Console to watch the
server boot into Intelligent Provisioning to configure the BIOS and deploy a firmware policy if specified.
You will be prompted to either install the Remote Console software, or launch it.
16. Once the Remote Console has launched, you can watch the server POST. The Custom POST message you defined in
the BIOS settings will take affect after the server completes its boot into Intelligent Provisioning.
53
17. After the server completes it’s POST, the server will be automatically instructed to boot into Intelligent Provisioning to
apply the SPP Baseline.
18. Once the firmware update has completed, the server’s Power State will change to Off. You are now able to install the
OS on your server.
Create Assigned Profile: One-Off Server Profile
2. Once on the Server Profiles screen, select the Create Profile button.
3. Provide a name for the Server Profile.
4. In the Server Hardware field, you will select the Enclosure Name and Bay ID that the profile will be assigned to, and the
Firmware Baseline (SPP). The firmware update will occur prior to the Server Profile being applied to the server.
Note
HP OneView does not currently support Server Profile inheritance. E.g. 1:Many Profile Assignment.
5. Add the needed Network Connections by clicking the Add Connection button, and either assign a Network or Network
Set to the Connection.
A. You can specify which FlexNIC to assign the Network Connection to, or leave it at the default of Auto. Auto will
apply the same Network Connection to Adapter mapping Virtual Connect does today.
6. Modify any of the other settings, Boot, BIOS, or Advanced.
7. Click Create or Create+ if you wish to create additional Server Profiles. Server profiles can only be assigned to servers
that are powered off.
Add New Blade to Enclosure (Optional)
In this section, you will need to insert a new blade into the enclosure. This will help you verify that a new blade is
automatically discovered in the enclosure by HP OneView. When a new blade is inserted into the enclosure, the Onboard
Administrator will register a Blade Insertion event, which will be forward to the HP OneView console. A discovery task will be
created, which HP OneView will attempt to configure the iLO for management.
1. Insert new blade into enclosure.
2. Navigate to the Enclosures Top Level Menu.
3. Examine the Device Bays panel to validate the new blade appears in the appropriate bay.
4. Once the new blade has been discovered, assign it a Server Profile.
54
Section D9: Environmental Management

With HP OneView, you can optimize the power and cooling requirements of your data center efficiently. While each individual
system, enclosure or PDUs in your data center can provide its power requirements and sometimes even a limited amount of
power consumption history, it is still difficult to understand the power and cooling requirements for your data center in a
holistic way.
In this section, you will go through how to configure your HP OneView so you can start investigating more about the overall
systems in your data center and their power & cooling capacities and consumption.
Physical data center configuration
In order to take advantage of analysis and management features for your environment, you first want your physical data
center environment to be accurately represented. You have the ability to match the physical placement of systems,
enclosures, racks and other unmanaged devices through HP OneView.
Add racks based on Location Discovery Services (LDS)
Racks are automatically created based on LDS. HP ProLiant Servers or HP BladeSystem enclosures mounted in HP
Intelligent Series Racks are automatically grouped in racks in the proper positions. The initial rack names are provided by
the Rack Serial Number. The height of a created rack is displayed as 42U unless the top-most device managed by HP
OneView is in a higher position. If a managed device is later added to a position about 42U, the rack height will be
automatically adjusted.
Add enclosures to racks without LDS
If no LDS is present, HP BladeSystem enclosures automatically create an enclosing rack in HP OneView during the discovery
process, based upon the name configured in the HP BladeSystem Onboard Administrator.
• Use of BladeSystem management stacking link cables up/down for all enclosures in a rack is encouraged – it causes a
single rack to be created per set of enclosures and the enclosures will be in the proper order in the rack. Specific slot
positioning must be provided by adjusting the positioning in the UI or via REST
• If BladeSystem management stacking links are not used – one rack is created per enclosure. Manually change the HP
OneView configuration to put the enclosures into a single rack and delete any duplicated racks.
1. To view the rack an enclosure is located in, select the Enclosures section from the main menu. After selecting the
correct enclosure from the main pane, the information in the Hardware section of the details pane allows you to see
the rack automatically created to house the enclosure.
55
Adding DLs to rack without LDS

If LDS is not present, racks are not automatically created for DL servers. DL servers may be added to racks previously
created via enclosure discovery or racks may be created manually and have servers added to them. For either option, begin
by navigating to the Racks screen.
1. To go to the Racks screen, select Racks in the main menu.
2. On the Racks screen, to create a rack either select +Add Rack button in the left panel or Add from the Actions pull-down
on the right of the screen.
OR
3. Once on the Add Rack screen, the screen details is segmented into the General and Layout sections. On the General
pane, enter the requested information for the rack hardware.
4. The Layout panel consists of a visual representation of the rack and its slots, a list of available devices and a search box
to find the desire systems and enclosures. From this panel, you can add, remove, and rearrange devices within the
56
rack and edit the device details. To place a device, drag and drop it in the desired location.
5. Once the rack has been configured, select Add to complete the setup or Add + if additional racks need to be created.
Creating a data center
HP OneView allows you to describe the physical locations of your racks and systems within your data center. After placing
systems in the racks, 3D data center maps can be created to accurately describe the racks location on the data center floor.
1. To go to the Racks screen, select Data Centers in the Facilities list of the main menu.
2. HP OneView automatically creates a default data center (Datacenter 1) during setup which serves as a holding place for
racks once created. All racks are listed under Datacenter 1 in the order they were created. A message is shown until
57
the default data center indicating it has not been configured.
3. If you wish to use the default Datacenter 1 for your actual data center, resolve the warning message by editing
Datacenter 1 and renaming/resizing it to match the data center floor (or portion thereof) you are going to be managing
with HP OneView. This process is described in subsequent steps. Alternately, you can remove Datacenter 1 and Add
one or more data centers as described next.
4. To add new data centers, use the + Add Data Center link on the Data Centers screen. The resulting screen details allows
you to input specific information regarding the data center and the racks it contains. Racks available for placement are
listed in the Unpositioned Racks field. This listing includes racks held in the unconfigured default Datacenter 1.
58
5. To edit an existing data center, select Edit in the Layout section of data center page.
6. The Layout panel of the Edit screen allows you to drag & drop racks on the grid from an overhead view.
7. For physically accurate positioning not aligned with the grid lines, enter the position and angle in the rack positioning
popup.
59
8. To remove any racks that are not part of the data center, drag them back to the unpositioned list or select them and
click the Remove link in the popup.
9. Once editing of the data center is complete, select the OK button to return to the data center screen to view the 3D
model of the data center.
Configuring power delivery topology for the data center
Configuring the physical setup for your data center is only half the picture. To get a complete understanding of your
environment, you can also configure its power delivery hierarchy. Building out your environment’s power topology helps
reduce downtime by eliminating wiring errors and identifying potential overloads. HP OneView enables you to create power
distribution device objects and describe the power source for one or more components in the rack. Below, configure the
rack-level power distribution for each rack.
Adding HP iPDU’s
1. Navigate to the Power Delivery Devices section from the Top Level Menu
60
2. To add HP iPDUs that power your previously discovered equipment, on the Power Deliver Device screen select + Add
power delivery device.
3. Enter the FQDN or IP address along with the login credentials needed for discovery.
4. Once the iPDUs have been discovered, view the rack in which the iPDU-powered equipment resides. The iPDUs will be
automatically depicted in the rack layout.
5. Edit the rack associated with the iPDU to set the iPDU core position properly.
6. Drag the iPDU to the upper or lower 0U space drop zones on the A/B side of the rack as appropriate.
7. Or specify the position via the device configuration popup accessible via the gear icon on the device.
61
Adding 3rd Party PDU’s or non-HP iPDU’s
1. If an iPDU is not being used, create one or more Rack PDUs to represent power capacity in the rack. On the Power
Delivery Device screen, select + Add power delivery device.
2. On the Add Power Delivery Device screen, select Rack PDU and specify the properties that will represent your PDU and
the power capacity it provides.
3. If you know the hardware the PDU will be providing power to, it can be added by selecting the Add Connections link on
the Add Power Delivery Device screen above. Once there, available hardware can be selected.
4. Next, navigate to Racks from the Top Level Menu.

5. Edit the rack layout associated with the newly created PDU to set its position properly by dragging components around
within the rack or from the Device Selection list.
Adding Unmanaged Devices
Unmanaged devices can be created for any devices that cannot be discovered by HP OneView but consume power or slots in
the rack.
62
1. Select the Unmanaged Device Top Level Menu.
2. Once on the Unmanaged Devices screen, select the +Add unmanaged device button.
3. Enter the specified information to represent the unmanaged device. Specify the maximum power value for the device
to enable capacity and consumption analysis of your power delivery system. Once all information is completed, click
the Add or Add+ button.
4. The device can then be added to any rack layout and associated with any power delivery device.
Section D10: Securing the Appliance with Active Directory/LDAP

•Configure Active
Directory or
OpenLDAP
•Configure
Directory Groups
HP OneView can be integrated with Microsoft Active Directory or other LDAP directories, like OpenLDAP. This section will
cover how to configure Active Directory authentication within the appliance.
63
You will need the following prior to configuring Active Directory settings within the appliance:
Table 10. Active Directory or OpenLDAP Checklist
SSL certificates installed on your Domain Controllers
FQDN of available Domain Controllers or LDAP Servers
Domain Security Groups for Server Admins (will map to

Specialized Server Administrator role)
Network Admins (map to Specialized Network Administrator

role)
Infrastructure Admins (map to Full Administrator role.)
Read-Only Users
1. Select the main menu option in the upper left, and choose Settings.
2. Within the Settings view, the Edit option for Security will be displayed when you mouse into that frame. Select the Edit
link.
64
3. Within the Edit Security window, click the Add directory button.
4. In the Add Directory window, you will need to specify the following:
• Directory Name
• Directory Type
• Search Context
– Field 1: CN for Active Directory, UID for LDAP Directories
– Field 2: Organizational Unit in Distinguished Name format (i.e. OU=Admins,OU=Contoso)
– Field 3: Top Level Domain Name in Distinguished Name format (i.e. DC=contoso,DC=com)
• Click the Add directory server button to add your Domain Controller FQDN and Base-64 Public Key Certificate used
for Server Authentication.
• The Username and Password fields are to validate the Directory configuration. A Valid user account must exist in
the Search Context you configured. You must specify the Canonical Name value of the user account.
Note
Starting with HP OneView 1.01, Field 2 can contain up to 4 Search Contexts. Referred to as multiple Relative Distinguished
Names (RDNs), a'+' symbol is used to provide different search contexts. For instance, the following OU’s could contain
different Administrator accounts and groups:
 OU=admins,OU=Finance,DC=Contoso,DC=com
 OU=admins,OU=Sales,DC=Contoso,DC=com
 OU=admins,OU=HR,DC=Contoso,DC=com
 OU=admins,OU=Corp,DC=Contoso,DC=com
You can combine the above Search Contexts into a single value:
 OU=admins,OU=Finance,DC=Contoso,DC=com+OU=admins,OU=Sales,DC=Contoso,DC=com+OU=admins,OU=HR,
DC=Contoso,DC=com+OU=admins,OU=Corp,DC=Contoso,DC=com
65
5. After the Directory has been configured, go back and Edit Security to set the Default Directory, and click OK to save the
settings.
66
6. Next, navigate to Users and Groups from the main menu.
7. In the Users and Groups view, select the Actions menu and choose Add Directory User or Group
8. In the Add Directory User or Group screen, provide the credentials to authenticate. Once authenticated, begin typing the
directory group name in the Group Name field. Select the group, and specify its role.
67
9. Repeat the same steps to add the remaining Directory Groups.

10. After you have configured your Directory Groups, you should log out by clicking the User button in the upper right of
the UI and select Logout.
11. On the logon page, you will notice a new field to choose. This is the Directory chooser. You can select from the
configured Directories and Local (if Local was not disabled in your Directory configuration.)
68
12. Log into appliance with a Server Admin user account
13. Navigate to Networks from the Top Level Menu, and notice the +Create Network button and Actions menu Networks
from the Top Level Menu, and notice the +Create Network button and Actions menu are unavailable.
14. Log into appliance with a Network Admin user account
69
15. Navigate to Server Profiles from the Top Level Menu, and notice the +Create Server Profile button and Actions menu is
no longer available.
Maintaining Your Environment

This segment will give you examples of how to maintain your HP OneView appliance. It will cover the regular maintenance
tasks that an administrator will encounter.
Section M1: Alerts and Monitoring

Prior to physical and power delivery configuration, HP OneView provides a Utilization panel where a summary of the current
usage of each metric available for a resource can be monitored. Each type of resource provides specific metrics that are
collected from the management processor and displayed. The values depicted provide the value of the metric during the
most recent five minute period.
Having configured the physical and power delivery topology of your environment, you can now begin to monitor and
analyze its use of power and cooling resources. Power utilization monitoring allows you to identify and eliminate areas of
waste while thermal monitoring helps reduce overcooling and fix hot spots.
1. The Dashboard, which is the default view when logging into the appliance, provides an overview of activity and alerts.
2. Select the desired hardware resource screen from the main menu.
70
3. The Utilization panel located within the details pane shows the metrics available for monitoring for the resource. The
utilization metrics available to be monitored depends on the resource type:
• Server hardware: CPU, power (including power cap) and temperature
• Enclosures: power (including power cap settings) and temperature
• Power Delivery Devices: power
4. Flyovers showing the past 24 hours worth of CPU, Power or Temperature data are available by moving the pointer over
the desired metric.
71
5. Selecting the Utilization panel heading or selecting Utilization from the view menu allows display and navigation of all
available history of a specified metric.
OR
6. Once selected, the details pane will show the first available metric for the device expanded. By default the last 24
hours of information is shown on the graph. However, the date bar below the graph allows selecting any available date
range to be displayed
72
7. Custom graphs can also be created. This custom graph allows two metrics to be plotted on the same graph allowing
comparison between the metrics.
8. HP OneView allows you to view areas in your data center that are insufficiently cooled due to various reasons such as
poor airflow, concentration of excessive heat output, or wrap-around airflow at the ends of aisles. Likewise, it is
possible to determine areas that are being overcooling and wasting cooling resources. HP OneView’s 3D visualization
of the data center shows the peak observed temperature of each rack the last 24 hours.
Viewing Activity, Alerts and Tasks

Various health alerts are recorded regarding the lifecycle management of your data center and IT equipment. This capability
enables you to be notified of events that may arise such as:
• New blade server inserted
• Create/Delete/Modify Networks
• Firmware Update
• Pre-Failure warnings
• Uplink Status of Logical Interconnects
• New potential overload conditions precipitated by addition of new hardware
• Thermal capacity of devices in rack exceed specified thermal limit
73
• Lack of power delivery redundancy to devices attached to power delivery devices
1. Select the main menu option in the upper left, and choose Activity.
2. This page is the master list of all activity within the appliance.
Pin out Filters
Expand/Collapse Item Alert Item
Assign Owner
Clear State
Add a Note to Activity Details
3. You can also expand the hardware resource (Server Hardware, Server Profile, Enclosure, Logical Interconnect, etc.) and
look at the alert view to see the problem description. The details from the alert can most times be used to identify and
help fix the problem.
74
Section M2: Add New Networks and Edit Server Profile

In this section you will add Networks to HP OneView and modify an existing Logical Interconnect Group. You will then add
the new Network or Networks to an existing Network Set or add a new Network Connection to an existing Server Profile.
Add Network(s)
1. Add a new Ethernet Network into the appliance. By adding a new Network, HP OneView will configure all Logical
Interconnects within the HP OneView appliance, but not configure the Uplink Set(s) or Logical Interconnect Group(s).
By looking at the Logical Interconnecet, you will notice the network(s) you added is a Local network.
75
2. Navigate to Logical Interconnect Groups, and add the new Network(s) to an existing Uplink Set.
3. Now that the Logical Interconnect Group has been updated, the Logical Interconnects that were created from importing
the Enclosure will report they are no longer consistent with the group. Navigate to the Logical Interconnect that
requires updating. Select the Actions menu, and then Update from group. Repeat for any other Logical Interconnects
that require updating.
76
4. Navigate to Network Sets and add the new Network to an existing Network Set.
Information
Adding a Network to a Network Set does not require a Server to be powered off, and will deploy the updated Network
Set configuration automatically.
5. Examine a Server Profile that contains a Network Connection assigned to the Network Set.
Edit Server Profile

Once a profile has been applied, you can edit the profile to make changes, and fix issues that may have been encountered.
Introduced in the HP OneView 1.05 release, you can edit existing Network Connections by modifying existing assigned
Network and/or Bandwidth without needing to first Power Off the server. Other Server Profile edits will require the Server
Profile to be Powered Off.
1. Verify the Server is powered off, if your appliance is not at 1.05 or newer.
2. Select the Actions menu, then select Edit.
3. Make the necessary changes to the server profile (i.e. Bandwidth adjustment, add a Network Connection, etc.)
4. Click the OK button to save the changes to the Server Profile.
5. Notice the server does not have its firmware reapplied, and only those changes are applied.
Section M3: Adding a New Enclosure

1. Select the main menu option in the upper left, and choose Enclosures.
77
2. Once on the Enclosure screen, select the +Add enclosure button.
3. Provide the IP address or FQDN of the Enclosure, with an Administrator account, select an Enclosure Group, and specify
the Firmware Baseline to apply. Selecting the Add or Add+ button, the enclosure will be discovered, and the OA
firmware will be updated to the version within the SPP.
4. During the Add Enclosure process, the Onboard Administrator firmware will be updated and the appliance will report
the Onboard Administrator cannot be reached. This is a normal message during the OA Firmware Update process. You
can see this error condition by viewing the Alerts of the Enclosure. This alert will be automatically cleared after the
Enclosure has been added.
78
5. After the Add Enclosure task has completed, the Enclosure State should read Configured.
Section M4: Adding a Ethernet Network

79
3. In the new window, provide the Name, select Ethernet as the Type, provide the VLAN ID, and bandwidth settings. Smart
Link will automatically be selected by default. Select Private Network if needed.
Note
HP OneView 1.05 supports Virtual Connect Active/Active Network Designs.
5. After the network has been created, it will be provisioned to all managed Virtual Connect Ethernet Interconnects. The
new network(s) is an “Internal” network, until it is assigned to an Uplink Set either at the Logical Interconnect Group or
Logical Interconnect.
80
Section M5: Adding a Fibre Channel Network

3. In the new window, provide the Name, select Fibre Channel as the Network Type, select the correct Fabric Type, and
modify Bandwidth allocation, Uplink Speed, Login Redistribution as needed.
4. Click the Create button to create the new Fibre Channel Network and close the Create Network dialog box.
81
Section M6: Adding an Ethernet Uplink to a Logical Interconnect

1. Select the Top Level Menu, and select Logical Interconnect.
2. Once on the Logical Interconnects screen, select the Edit option from the Actions menu.
3. In the new window, click the button Add Uplink Set.
4. Enter a name for the Uplink Set, Select Ethernet as the Network Type, select the correct Add Networks button
82
5. Select the network that will added to the new Uplink Set, then click the Add button.
6. Select the Add uplink ports button.
7. Select the ports that will be used for the new uplink. Click the Add button.
83
8. Click the Create button to create the new Ethernet Uplink
9. Click the OK button to enable the new Ethernet Uplink
Section M7: Adding a Fibre Channel Uplink

1. Select the Top Level Menu, and select Logical Interconnect Groups.
84
2. Once on the Logical Interconnects screen, select the Edit option from the Actions menu.
3. In the new window, click the button Add Uplink Set.
4. Enter a name for the Uplink Set, Select Fibre Channel as the Network Type, select the correct Fibre Channel network
from the dropdown list Add Networks button
85
5. Under the Uplink Ports section, select the interconnect module that will be used for the new network using the drop
down menu.
6. Using the checkboxes, select the ports that will be used
86
7. Select the Create button.
8. Click the OK button to apply the changes to the Logical Interconnect.
87
9. Click the OK button to create the new Ethernet Uplink Set by saving the Logical Interconnect.
Section M8: Removing Networks from a Server Profile

In this Use Case you will remove a network from the HP OneView and modify an existing Logical Interconnect Group.
Add Network(s)
1. Navigate to Server Profiles in the console
2. Select the server profile you want to edit from the menu on the left
88
3. Select the Actions menu, then select Edit.
4. Remove the desired network from the server profile by selecting the X next to the network settings
5. Click the OK button to save the changes to the Server Profile.
Section M9: Creating New Users

HP OneView supports the methodology of differing roles within a Converged Infrastructure. In this section we will create a
new user for the HP OneView environment.
1. Select the Top Level Menu, and navigate to Users and Groups in the console
2. From the left hand menu, select the +Add User button.
3. Provide a login name, Full name (optional), then enter and confirm the password that will be used for the account.
Select the type of Role that this user will have. Specialized accounts can be limited to Backup functions, Network
functions or Server functions. Full accounts are administrators for all segments. Read only accounts will be able to
view information within HP OneView but not change any information. Contact Email, Office and Mobile Phone numbers
89
can be added if desired.
4. Select Add button to create the account.
Section M10: Deleting Existing Users

HP OneView supports the methodology of differing roles within a Converged Infrastructure. In this section we will delete an
existing user in the HP OneView environment.
2. Select the user that needs to be deleted from the left hand menu
3. Now that the correct account has been selected, select Remove from the Actions menu
90
4. Confirm your selection by selecting the Yes, remove button to delete the account.
Section M11: Changing User Permissions

HP OneView supports the methodology of differing roles within a Converged Infrastructure. In this section we adjust the
permissions for a user within the for the HP OneView environment.
2. Select the user you want to edit from the left hand menu
3. Now that the correct account has been selected, select Edit from the Actions menu.
91
4. Edit the information that needs to be changed.
5. Click the OK button to save the changes that have been made.
Section M12: Adding a New Blade to an Enclosure and Discovering New Server Hardware
Types
As it was discussed in the first chapter, Deploying Your Appliance, Server Hardware Types are automatically discovered and
defined by HP OneView when a new server is added to the environment. This section outlines how to add a new server and
the expected behavior. When a new blade is inserted into an HP OneView managed enclosure, the OA will register a Blade
Insertion SNMP event, which will be forward to HP OneView. A discovery task will be created, which HP OneView will attempt
to configure the iLO for management.
1. Insert new blade into the enclosure
2. Select the Top Level Menu, and navigate to Enclosures in the console
3. On the left hand side select the desired enclosure
92
4. Change to the Activity view of the enclosure to see the Blade Inserted event.
5. After the blade is inserted and discovered, from the Top Level menu select Server Hardware Types. If the new server is
a new model, or has different connectivity layout (i.e. different FlexLOM or mezzanine options installed) than other
managed servers, the new hardware type would now be listed.
Section M13: Adding New Racks Based on Location Discovery Services

Racks are automatically created based on LDS. HP ProLiant Servers or HP BladeSystem enclosures mounted in HP
Intelligent Series Racks are automatically grouped in racks in the proper positions. The initial rack names are provided by
the Rack Serial Number.
Section M14: Adding Enclosures to Racks without Location Discovery Services

If no LDS is present, HP BladeSystem enclosures automatically create an enclosing rack in HP CI Mgmt during the discovery
process, based upon the name configured in the HP BladeSystem Onboard Administrator.
• Use of BladeSystem management stacking link cables up/down for all enclosures in a rack is encouraged – it causes a
single rack to be created per set of enclosures and the enclosures will be in the proper order in the rack. Specific slot
positioning must be provided by adjusting the positioning in the UI or via REST
• If BladeSystem management stacking links are not used – one rack is created per enclosure. Manually change the HP
OneView configuration to put the enclosures into a single rack and delete any duplicated racks.
1. To view the rack an enclosure is located in, select the Enclosures from the main menu.
2. Select the correct enclosure from the navigation pane on the left
93
3. The information in the General section of the details pane allows you to see the rack automatically created to house
the enclosure.
Section M15: Adding Rack Servers (DL’s) to Racks without Location Discovery Services
If LDS is not present, racks are not automatically created for DL servers. DL servers may be added to racks previously
created via enclosure discovery or racks may be created manually and have servers added to them. For either option, begin
by navigating to the Racks screen.
1. To go to the Racks screen, select Racks in the main menu.
2. On the Racks screen, to create a rack either select Add Rack button in the left panel or Add from the Actions pull-down
on the right of the screen.
OR
3. Once on the Add Rack screen, the screen details is segmented into the General and Layout sections. On the General
pane, enter the requested information for the rack hardware.
4. The Layout panel consists of a visual representation of the rack and its slots, a list of available devices and a search box
to find the desire systems and enclosures. From this panel, you can add, remove, and rearrange devices within the
94
rack and edit the device details. To place a device, drag and drop it in the desired location.
5. Once the rack has been configured, select Add to complete the setup or Add + if additional racks need to be created.
Section M17: Adding a Service Pack for ProLiant (SPP) Bundle
2. Select Add Firmware Bundle button.
3. In the Add Firmware Bundle screen, click on the Choose File button, and select the SPP ISO to upload. Once selected,
click the Stat Upload button. Firmware bundles (SPPs) can also be drag-and dropped from Windows environments.
You can navigate away from the Firmware Bundle screen to other areas within the UI, as the upload process is a
95
background process within the browser.
Note
Do not close the browser window until the Firmware Upload task has completed. You can click on the Close button in the
Add Firmware Bundle dialog as the upload is a background thread within the web application.
4. After the SPP has been uploaded, you can examine the contents
Section M18: Updating the Firmware Baseline for Existing Servers with Profiles
Assigned
Note
This method is for single unit, offline firmware updates only. To perform online firmware updates, please use HP Smart
Update Manager. http://www.hp.com/go/SUM.
1. Ensure that the firmware bundle is uploaded to the HP OneView appliance

96
3. Once on the Server Profiles screen, select the Edit from the actions menu.
4. In the General section of the Edit Profile page, select the Firmware baseline to be used for the Server Profile.
5. Click OK to apply the changes.
97
6. The firmware update will begin
Section M19: Managing Multiple Firmware Images in the Same Enclosure

Because HP supports its SPP bundles for 12 months. It may be necessary to have different servers within the same
enclosure on different SPP bundles. This enables a customer to update the infrastructure ahead of time and update the
servers during their normal maintenance window.
2. Select Add Firmware Bundle button.
3. In the Add Firmware Bundle screen, click on the Choose File button, and select the SPP ISO to upload. Once selected,
click the Stat Upload button. Firmware bundles (SPPs) can also be drag-and dropped from Windows environments.
You can navigate away from the Firmware Bundle screen to other areas within the UI, as the upload process is a
98
background process within the browser.
4. Select the Top Level Menu, and navigate to Enclosures in the console
5. Select the correct enclosure from the navigation pane, then select Update Firmware from the actions menu.
99
6. On the Update firmware screen select the correct Firmware Baseline and select Enclosure to update only the enclosure
firmware.
7. Click OK to begin the firmware update.
8. Verify that the enclosure firmware update is complete
100
9. Select the Top Level Menu, and navigate to Logical Interconnect in the console
10. Select the Logical Interconnects for the enclosure from the navigation pane
11. Select Update Firmware from the actions menu.
12. On the Logical Interconnect Update firmware screen select the option to Update Firmware option then select the correct
Firmware Baseline. Click OK to apply the firmware.
101
13. Verify that the Logical Interconnect firmware update is complete.
14. Next, navigate to Server Profiles from the top level menu. Select the correct Server Profile from the navigation pane.
15. Verify the Server Power is Off, and select Edit from the actions menu.
102
16. On the Edit Server Profile screen select the correct firmware baseline from the Firmware Baseline dropdown box to be
used for this Server Profile. Click OK to apply the firmware.
17. Verify that the firmware update on the Server Profile is complete
18. Verify firmware A is still on previous firmware
Section M20: Modifying Virtual ID Pools

HP OneView has the ability to pool address ranges just like Virtual Connect Enterprise Manager does today. However, HP
OneView provides many more address ranges by using Locally Administered Addresses4, including Auto Generated pools
that can greatly expand the pool capacity. By default, there are ~1 million ID’s per MAC and WWN pools.
4
http://en.wikipedia.org/wiki/MAC_address, review Address Details section.
103
2. On the Settings window, you will see a section called Addresses and Identifier.
3. When you click on the heading, you will see which pools have been automatically created, and the current allocation.
You can select the Add auto-generate button to create a new range of addresses for the pool, or add a custom range.
104
Section M21: REST API

REST (Representational State Transfer) is a web service format that uses basic Create, Read, Update and Delete (CRUD)
operations that are performed on resources using HTTP POST, GET, PUT and DELETE. To learn more about general REST
concepts, see:
http://en.wikipedia.org/wiki/Representational_state_transfer
HP OneView has a resource-oriented architecture that provides a uniform REST interface. Every resource has one Uniform
Resource Identifier (URI) and represents a physical device or logical construct, and may be manipulated using REST APIs. To
view the list of resources, see HP Converged Infrastructure Controller REST API Reference located in the Online Help of the
appliance [https://{ip}/help/cic/en/content/images/api/].
Resource operations
Basic Create, Read, Update and Delete (CRUD) operations are performed on the appliance resources via the standard HTTP
POST, GET, PUT and DELETE methods. RESTful interfaces are based on the World Wide Web standards, thus most modern
web servers can support these operations without modification.
Restful APIs are stateless. The resource state is maintained by the resource manager and is reported as the resource
representation. Any application state must be maintained by the client and it may manipulate the resource locally, but until
a PUT or POST is made, the resource as known by the resource manager is not changed.
Table 10. REST HTTP Operations
Operation HTTP Verb Description
Create POST URI <Payload = Resource data> New resources are created using the POST operation and
including relevant data in the payload. On Success the
Resource URI is returned.
Read GET URI Returns the requested resource representation(s)
Update PUT URI <Payload = Update data> Update an existing resource using the update data.
Delete DELETE URI Delete the addressed resource
URI format
All the appliance URIs point to resources and the client does not need to modify or create URIs. The URI for specific resource
is static and follows this format: https://{appl}/rest/{resource name}. The three parts are described below.
Table 11. URI Format
https://{appl} The appliance address.
/rest Type of URI.
/{resource name] Name of the appliance resource such as server-

profile.
Data transfer format

The appliance resources support JSON (JavaScript Object Notation) as the standard for exchanging data using a REST API. If
JSON is not specified in the REST API call, then the default is JSON.
To learn more about JSON, go to www.json.org.
Accessing the ReST API with PowerShell
The HP OneView PowerShell Library is available for download at https://hponeview.codeplex.com, both the source code and
a pre-built installer. The library requires the Windows Management Framework 3.0 (aka PowerShell 3.0) to be installed, and
the .Net 4.0 Client Framework. The HP OneView POSH Library Installer will assist you with the installation of these two
required components if not found on the system.
105
Please visit the HP OneView Online Documentation page (https://hponeview.codeplex.com/documentation) for all available
CMDLETs and the associated help.
Using PowerShell
Note
The following example assumes the HP OneView POSH Library is installed with the available install package.
The HP OneView PowerShell library is a self-contained module that you first need to import, or add to your PowerShell
Session Profile. After the module has been successfully imported, you must first execute Connect-HPOVmgmt in order to
authenticate to the appliance. You can then execute other cmdlets to perform the desired action.
1. Execute Import-Module HPOneView
A. Example:
PS C:\Users\Administrator> Import-Module HPOneView
Welcome to the HP OneView POSH Library, v1.05
To get a list of available CMDLETs in this library, type : Get-Help hpov

To get help for a specific command, type: get-help [verb]-HPOV[noun]
To get extended help for a specific command, type: get-help [verb]-HPOV[noun] –full
If you need further help, please consult one of the following:
• Get-Help about_HPOneView
• Oneline documentation at https://hponeview.codeplex.com/documentation
• Oneline Issues Tracker at https://hponeview.codeplex.com/workitem/list/basic
Copyright (C) 2014 Hewlett-Packard
2. Execute the Connect-HPOVmgmt CMDLET

A. Example
[HPONEVIEW]: [Not Connected] PS> Connect-HPOVmgmt -appliance appliance.example.com –user
Administrator –password hp1nvent
[HPONEVIEW]: [email protected] PS>
3. Once you have authenticated to the appliance, you can execute different CMDLETs provided by the library
A. Example
[HPONEVIEW]: [email protected] PS> New-HPOVNetwork –Type “Ethernet” –Name
“Blue” –VLANID 100
Creating Blue Ethernet Network
Accessing the ReST API with Python

Python comes with a few libraries that can complete REST requests like httplib2 and urllib2, these libraries are rather
difficult to use and require a lengthy learning curve. Another python library called "Requests" has solved the learning curve,
cleaned up REST requests and made them very easy to use. For a full comparison take a look at
http://isbullsh.it/2012/06/Rest-api-in-python/
This overview of using Python to create REST requests will feature the Requests library.
Requests
Requests (http://docs.python-requests.org/en/latest/) is an easy to use REST request Python library.
How to get Requests
To get requests follow the steps on the Requests website here: http://docs.python-
requests.org/en/latest/user/install/#install
The best method would be to use pip (the python package manager) to install requests:
> pip install requests
106
Creating and executing a request

To execute a request is very simple. First look at the following code:
uri = '/rest/login-sessions'
method = 'POST'
data = {
'userName': username,
'password': password,
}
headers = {
'Accept': 'application/json',
'Content-Type': 'application/json',
'Accept-Language': 'en_US',
}
url = 'https://' + hostname + uri
response = requests.request(method, url, data=json.dumps(data),
headers=headers, verify=False)
A request is made up for 4 items:

• Method - HTTP Method (e.g. POST, PUT, GET, etc.)
• URL - URL for the new Request object.
• Body (or data) - Any data we want to pass in
• Headers - HTTP headers, including request type and authentication key
Example: Logging In
Below is a fully working example of using Python + Requests to login to an appliance and collect the session ID:
#!/usr/bin/env python
# © Copyright 2013 Hewlett-Packard Development Company, L.P.
import json
import requests
def main(hostname, username, password):
uri = '/rest/login-sessions'
method = 'POST'
data = {
'userName': username,
'password': password,
}
headers = {
'Accept': 'application/json',
'Content-Type': 'application/json',
'Accept-Language': 'en_US',
}
url = 'https://' + hostname + uri

response = requests.request(method, url, data=json.dumps(data),
headers=headers, verify=False)
if response.status_code == 200:
print (response.json()['sessionID'])
else:
print (response.json()['errorCode'] + ': ' + response.json()['message'])
if __name__ == '__main__':
hostname = 'host.domain.com'
username = 'administrator'
password = 'password'
main(hostname, username, password)
107
Section M22: Creating a Support Dump

As with any product, occasionally there will be a situation that will require you to engage support. HP OneView provides a
Support Dump option to help with this process. There are two Support Dump options, and each contain different
information: the Appliance and Logical Interconnects.
2. Select the Actions menu option, and select Create Support Dump. It may take a minute or two to collect the Support
Dump logs. The Support Dump may also be very large. This Support Dump collects information about the Appliance.
3. Save the .SDMP file.

4. Nagivate to Logical Interconnects from the Top Level Menu.
108
5. Select Create Support Dump from the Actions menu. This will collect support log files from the Virtual Connect
modules.
6. Save the .SDMP file.

7. Contact your HP Support Representitive and provide the information collected above.
109
Additional Resources
http://www.hp.com/go/OneView/docs
HP OneView Online Help
HP OneView Release Notes
HP OneView Support Matrix
HP OneView Installation Guide
HP OneView User Guide
HP OneView REST API Reference
HP OneView Firmware Management White Paper
Transitioning a Virtual Connect Configuration to HP OneView
http://www.hp.com/go/VirtualConnect
Virtual Connect Command Line User Guide
Virtual Connect Enterprise Manager User Guide
Virtual Connect Enterprise Manager Command Line User Guide
http://www.hp.com/go/oneviewcommunity
HP OneView Community Forums
https://hponeview.codeplex.com
HP OneView PowerShell Library
https://github.com/HewlettPackard/python-hpOneView
HP OneView Python LIbrary
Learn more at
hp.com/go/HPOneView
Sign up for updates

hp.com/go/getupdated Share with colleagues Rate this document
© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for
HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Windows PowerShell® is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.
Doc ID: c04040086 March 2014

HP Oneview Deployment and Management Guide v1

Uploaded by

Copyright:

Available Formats

HP Oneview Deployment and Management Guide v1

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 Oneview Deployment and Management Guide v1

Uploaded by

Copyright:

Available Formats

Technical Whitepaper

HP OneView Deployment and

Click here to verify the latest version of this document

Section M9: Creating New Users .......................................................................................................................................... 89

Welcome to the Quick Start, Deployment and Management Guide for HP

First Time Configure Discover Upgrade Server Environment Appliance

HP OneView 1.05 Features

Table 1. HP OneView 1.05 Features

HP OneView 1.0 Features

Table 2. HP OneView 1.0 Features

Logical Interconnect Groups VC module configuration with uplinks

Server Hardware Types Inventory of your standardized hardware configurations

Table 2. Supported Browsers

Internet Explorer 9 and 10

Mozilla Firefox 14 or newer

Google Chrome 21 or newer

Hardware Firmware Minimum Requirements

Table 3. Minimum Firmware Requirements

Onboard Administrator 3.00 or newer

iLO4 1.01 or newer

iLO3 1.20 or newer

Virtual Connect 3.15 or newer

Table 4. Post Import Firmware Minimum Version

Onboard Administrator 4.01

Virtual Connect 4.10

Table 5 shows the HP OneView 1.0 and 1.05 Configuration Maximums.

Table 5. Supported Maximums

Total Servers 640

Servers per Enclosure 16

Total Interconnects 160

Total Enclosure Groups 40

Total Server Profiles 740

Assigned Server Profiles 640

Total Unassigned Server Profiles 100

HP OneView User Interface Overview

Details Pane Activity Window

HP OneView Virtual Connect Management Architecture Overview

Deploying Your Appliance

Section D1: First Time Setup

Table 6. Installation Checklist

Task Completed? (Y|N)

Have a supported vSphere 52 host for appliance

Have Static IP Address, or DHCP Static Reservation

Have DNS A and PTR Records created

Figure 2. Obtain the Virtual Machine IP Address

Figure 4. License Agreement

Figure 5. HP Support Access Opt-In

Table 7. Default Credentials

Figure 6. Login Page

Figure 7. Change Administrator Password

Figure 8. Configure Appliance Networking

Section D2: Firmware Repository

2. Examine the default SPP Baseline

Section D3: Licensing OneView

2. Open the Actions menu, and select Add License.

Section D4: Network Configuration

Table 8. HP OneView Network Configuration Checklist

Task Completed? (Y|N)

Collect the Virtual Connect Module Types