Anda di halaman 1dari 7

HP BladeSystem Matrix

Solution Overview
Implementation overview

Part Number 510958-001

April 2009 (First Edition)
© Copyright 2009 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.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor’s standard commercial license.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

Intended audience
This document is for a user or customer who has recently purchased an HP BladeSystem Matrix Starter Kit.
At this stage, you are likely coordinating with the HP Technology Services or authorized partner who is
implementing the BladeSystem Matrix Starter Kit into your environment. Once your initial BladeSystem
Matrix environment has been implemented, it is assumed you will be involved in tasks such as managing
the servers and storage in this environment. HP assumes you are qualified in the servicing of computer
equipment and trained in recognizing hazards in products with hazardous energy levels.
HP BladeSystem Matrix - Implementation

Congratulations on buying HP BladeSystem Matrix. BladeSystem Matrix is an infrastructure solution that
optimally creates an Adaptive Infrastructure environment so that users can achieve an operationally
efficient data center infrastructure without high upfront or ongoing costs. It is built with HP BladeSystem c-
Class, Virtual Connect, Insight software, HP StorageWorks, and Factory and Services capabilities. For
more information on HP's Adaptive Infrastructure vision, see
( For more information about BladeSystem Matrix, see (
This document provides an overview of the implementation of an HP BladeSystem Matrix environment.

HP BladeSystem Matrix - Implementation overview 3

Implementation overview process

Pre-order phase
The BladeSystem Matrix process simplifies all elements of deploying an adaptive infrastructure by using
standardized yet flexible building blocks. Tools and guidance are available to help customers determine
how large and how to plan an order for a BladeSystem Matrix infrastructure. Customers can utilize the
pre-sales consulting resources of HP and authorized partners to plan and specify requirements.

Order phase
The method for purchasing BladeSystem Matrix is simple. A customer starts by ordering a Starter Kit,
which contains the infrastructure needed for a fully-working environment supporting up to 16 server
blades. Add Expansion Kits at the same time or add these later to expand your BladeSystem Matrix
infrastructure with additional infrastructure and server blades. The management host implemented in the
Starter Kit simply extends its domain to manage additional infrastructure that might be added with more
Expansion Kits.

HP BladeSystem Matrix - Implementation overview 4

HP factory fulfillment
Factory integration and configure-to-order services: With all BladeSystem Matrix Starter and Expansion Kit
orders, the following services are included:
• Factory services to default configure, rack, and cable the infrastructure in a rack.
• Firmware verification and updates for the entire solution being purchased (the BladeSystem Matrix
kits and the supported blades and options purchased with those kits) to the latest current
BladeSystem Matrix firmware release set. This ensures that the BladeSystem Matrix solution will leave
the factory with the correct levels of firmware needed for the end-to-end solution to be successful.
• Coordination of hand-off to Technology Services (TS) or authorized partner. A TS or partner project
manager is assigned for managing pre-engagement and assigning a team of engineers to perform
the implementation service at the customer's site.
Factory Express custom configuration services are added to the order if a HP StorageWorks 4400
Enterprise Virtual Array configuration is also purchased with the Starter (or Expansion Kits), or if any other
custom factory services are needed. Factory Express uses its standard processes for capturing customer
intent and requirements, as well as providing order verification services.

Implementation service project manager assignment

When an order is placed, HP automatically triggers the assignment of a BladeSystem Matrix
implementation service project manager who is responsible for coordinating and planning the delivery
and onsite implementation service into the customer's environment. This project manager also coordinates
the preinstallation checklist.

Pre-installation checklist
The implementation service project manager mentioned in the previous section engages with the user on a
pre-installation checklist to ensure that when the BladeSystem Matrix physical infrastructure arrives, the
onsite implementation service can be started without any delays. This also ensures smooth integration with
your existing environment.
Although largely self contained, a BladeSystem Matrix infrastructure has some key integration points into
a user's IT environment. This preinstallation consulting is an opportunity for the user to work closely with
HP BladeSystem Matrix solution experts to define and coordinate in these areas:
• Physical footprint, power and cooling — A BladeSystem Matrix Starter Kit is delivered in a rack and
therefore entails physical location, power, and cooling considerations.
• Central management server (CMS) host server network connectivity and related properties —
Required properties and network connectivity for the CMS are coordinated ahead of time as part of
the preinstallation checklist.
• Network connectivity — The physical and virtual server resources in a BladeSystem Matrix
infrastructure have network configuration requirements that must be planned to meet the user's
requirements. These include physical networks and VLAN connectivity, subnets, redundancy, and so
on. Access and information related to network services such as DNS, DHCP and others are
• Fibre Channel Storage Area Network (SAN) connectivity — The physical and virtual server resources
in a BladeSystem Matrix infrastructure also have Fibre Channel SAN and boot from SAN
requirements. These include physical SAN connectivity and zoning, and LUN presentation.

HP BladeSystem Matrix - Implementation overview 5

• Fibre Channel SAN target array — If the recommended StorageWorks EVA4400 SAN is purchased
with the BladeSystem Matrix Starter Kit, it is factory integrated for BladeSystem Matrix and is
preconfigured with LUNs prior to shipment to the user's site. However, if the EVA4400 is not
purchased and the user wants the BladeSystem Matrix solution to connect to an existing certified
SAN array, then this coordination takes place to ensure readiness for present LUNs for the
BladeSystem Matrix infrastructure.
• Other considerations also part of the checklist include having operating system images and license
keys ready (including images and license keys for the virtualization hypervisor host server), questions
regarding existing or separate hosts for server deployment (Rapid Deployment Pack), hypervisor
usage and hypervisor management (for integration with HP BladeSystem Matrix), and so on.
• Any devices ordered separately from the full BladeSystem Matrix order need to be appropriately
installed in racks and configured accordingly.
• The user also needs to make available their technical resources who are knowledgeable in
hypervisor host server environments and networking/SAN environments being utilized or integrated
with the BladeSystem Matrix environment.

Physical delivery
After delivery to the user's site, implementation service engineers from HP or an authorized partner assist
in unpacking and inspecting the preracked and precabled BladeSystem Matrix physical infrastructure for
damages, and begin the process of integrating it into the user's environment.

Onsite implementation service

These steps are included in the onsite Implementation Service for the BladeSystem Matrix Starter Kit:
1. After delivery to user's site, unpack and inspect for damages.
2. Integrate hardware in to users environment, power, network cabling.
3. Install and configure the central management server (CMS).
Includes installation and configuration of the software required for management by HP SIM (e.g.
PSP, ESX Management Agent, OpenSSH)
4. Install and configure HP Insight Rapid Deployment software (RDP).
5. License and configure the remaining software components.
o HP Insight Control Environment Suite (ICE)
o HP System Insight Manager (HP SIM)
6. Configure iLO 2 Advanced for BladeSystem.
7. Configure and setup managed nodes.
8. Integrate Insight Manager.
o HP Virtual Connect Enterprise Manager software (VCEM) — 1 VC Domain Group
o HP Insight Dynamics - VSE suite for ProLiant
9. Discover resources by Vman.
10. Integrate the CMS with an existing hypervisor management console.
11. Configure logical server definitions for the blade hosts and the virtual machines (VMs).
o HP Insight Orchestration software (HPIO)

HP BladeSystem Matrix - Implementation overview 6

o HP Insight Recovery software (installation and licensing only)
12. Deploy operating systems using HPIO and RDP to configured LUNs on the StorageWorks EVA 4400
SAN or an existing SAN.
o 1 HP server blade running a native OS of the user's choice (Microsoft® Windows® or Linux) on
a boot LUN
o 2 HP server blades each running a single hypervisor of the user's choice (VMware or HyperV),
each on their own boot LUN (licenses are user provided)
13. Configuration of up to two VMs.
o 1 HP server blade installed and configured to be a target for a blade move
14. Configure operating systems to boot from SAN.

1. Navigate through installed components and all management software.
2. Review the configured hardware components and their configuration.
3. Review the completed system topology.
4. Explain how to call HP for support.
5. Discuss availability of additional services, educational services, etc.
6. Demonstrate BladeSystem Matrix.

Ongoing operations
For more information, see the step-by-step use case guide.

HP BladeSystem Matrix - Implementation overview 7