Understanding the HP Blade System Matrix Technology

8/4/2019 Understanding the HP Blade System Matrix Technology

1/28

Understanding the HP BladeSystem Matrix

technology

Abstract .............................................................................................................................................. 2Introduction......................................................................................................................................... 2Overview: HP BladeSystem Matrix......................................................................................................... 3Important terms.................................................................................................................................... 5How BladeSystem Matrix is used........................................................................................................... 6Provisioning workloads in a shared services infrastructure ..................................................................... 7

Creating resource pools ................................................................................................................ 7Populating storage pools ............................................................................................................... 8Designing the infrastructure and creating templates .......................................................................... 9Requesting infrastructure services.................................................................................................. 10

Approval and provisioning .......................................................................................................... 11 Managing provisioned services.................................................................................................... 12

Continuously optimizing the infrastructure with capacity and power management.................................. 12Ongoing capacity management................................................................................................... 12Consolidation planning with what-if scenarios................................................................................ 12

Advanced power management: dynamic power capping................................................................ 13 Protecting continuity of services using built-in disaster recovery capabilities........................................... 14

Disaster recovery........................................................................................................................ 14Enabling technology .......................................................................................................................... 14

BladeSystem c-Class hardware ........................................................................................................ 14Virtual Connect .......................................................................................................................... 15

Storage technologies...................................................................................................................... 17Integrated management through Insight Dynamics software................................................................. 17Integrating Matrix into customer environments ................................................................................... 19

Compatible with existing networks................................................................................................ 19Compatible with existing SANs.................................................................................................... 19Support for most common operating systems and hypervisors .......................................................... 20Best practice application templates............................................................................................... 20Integration with enterprise management systems ............................................................................ 20

Security......................................................................................................................................... 20

Purchase and delivery ........................................................................................................................ 21Summary and conclusion.................................................................................................................... 23

Appendix: Matrix use cases................................................................................................................ 25 Additional use cases ...................................................................................................................... 27

For more information.......................................................................................................................... 28


2/28

2

Abstract

This whitepaper describes the HP BladeSystem Matrix solution, with a focus on how the solutiondelivers shared IT infrastructure servicesimproving the speed and reliability of service delivery whileincreasing IT efficiency and lowering associated costs. The paper includes a discussion of keyarchitectural concepts and enabling technologies, as well as a brief overview of the purchaseprocess.

HP BladeSystem Matrix is a complete solution implementing the HP Converged Infrastructure strategy.It is based on a shared services model, using pools of compute, storage, and network resources.Matrix integrates proven technologies to provide a complete platform upon which infrastructureservices can be readily provisioned and adjusted to meet changing business demands. The Matrixsolution is designed to be easily purchased, quickly deployed, and to integrate seamlessly intoexisting environments.

This document is intended for IT architects and directors and otherreaders who are familiar withcurrent HP BladeSystem offerings and existing server virtualization technology. The content shouldassist IT architects and directors who have an interest in understanding how BladeSystem Matrix mighbenefit their IT environments with more flexible, efficient use of physical and virtual IT resources.

IntroductionWhile many advances have been made in IT infrastructure to improve performance and availability,IT departments still struggle to respond to increasing business demands yet hold the line on costs. Theeffort to meet these demands has frequently led to IT sprawla condition in which computingresources proliferate throughout the business, but remain underutilized and too hardwired to be easilyredeployed when business needs change. Operating and maintaining those resources ties up ITdollarspersonnel costs for server management and administration can be as much as 80% of an ITbudget.1 There is a tremendous need to free up the personnel focused on operations and make themavailable to serve more strategic objectives and to drive innovation.

Companies are increasingly employing virtualization and automation to improve the flexibility and

use of computing resources. But these efforts have not yet eliminated the issues of over-provisioningand complexity. Too frequently, IT resources are dedicated to a particular application or business unitand any excess capacity remains unavailable for other uses. A shared services model enables IT toaddress these issues. IT staff can consolidate physical and virtual servers, storage, and network assetsinto pools of virtualized resources. These resource pools can be shared and managed to host sets ofinfrastructure services, which typically map to application services, including complex multi-tierapplications. IT personnel can flexibly provision and re-provision services, and can confidentlyoptimize the underlying resources for performance, resiliency, and efficiency. Moreover, companiescan achieve the flexibility and efficiency of a shared services model without giving up needed controlsthat reside in centers of data center expertise, such as server, network, storage, and facilitiesadministration.

HP is enabling a shared services model with its flagship Converged Infrastructure solution: HPBladeSystem Matrix. With BladeSystem Matrix and its management software, IT departments candeliver infrastructure services to customers or business units faster, more predictably, more efficiently,and with lowered costs.

1IDC White Paper Sponsored by HP, Realizing TCO Savings with HP BladeSystem Virtual Connect Flex-10Technology, Doc #218222, May 2009


3/28

3

Overview: HP BladeSystem Matrix

HP BladeSystem Matrix makes use of industry-standard, modular components, but it is far more thansimply a collection of components. In a single Converged Infrastructure platform, Matrix integratestechnologies from across the HP enterprise portfolio that have been proven in the marketplace toprovide value in demanding datacenter environments. Matrix also incorporates the offerings ofleading application, management, network, and storage partners, so that the solution fits seamlesslyinto diverse customer environments and works with all traditional application workloads.

HP BladeSystem Matrix is comprised of one or more BladeSystem c7000 enclosures, server blades,and shared storage, sized to each customers requirements, as well as all of the managementsoftware needed to provision, optimize, and protect the infrastructure. Matrix arrives at the customersite as a factory-integrated solution. Each Matrix solution also includes HP on-site implementationservices and training, enabling the customer to begin realizing the value of Matrix and the sharedservices model immediately.

Matrix supports the full range of HP ProLiant and Integrity full-height and half-height server blades andis scalable to over 1500 managed systems (virtual machine and physical machine instances). TheStorageWorks 4400 Enterprise Virtual Array (EVA4400) can be factory integrated (recommendedoption) or Matrix can be connected to newly purchased or existing HP StorageWorks or supported

third-party Fibre Channel storage area networks (SANs).The Matrix management console, built on HP Insight Dynamics, combines automated provisioning,capacity planning, disaster recovery, and a self-service portal. Matrix can be easily incorporated intoexisting data center environments: Virtual Connect modules in the BladeSystem enclosure enableMatrix to be connected to any standard Ethernet network or N_Port ID Virtualization (NPIV)-capableFibre Channel fabric and the platform is compatible with a range of operating systems andhypervisors. Figure 1 provides a solution diagram of HP BladeSystem Matrix.


4/28

Figure 1: Solution diagram of HP BladeSystem Matrix

The infrastructure orchestration capabilities provided in Matrix (Figure 2) enable the shared pools ofservers, storage, power, and network connectivity to be provisioned and re-provisioned, based ondefined templates, as needed. An IT architect or designer uses a graphical designer tool to build andpublish infrastructure service templates incorporating physical and virtual servers, storage, networks,and the connections between them. Typically each template represents the complete infrastructureneeded to host a customers specific application service, such as Microsoft Exchange, Oracle Real

Application Clusters, an enterprise resource planning solution, or even a custom application. Acatalog of published service templates is then available to users; using a simple self-service portal,users can request an instance of a service template to be automatically provisioned. Through itsinfrastructure orchestration capabilities, Matrix provides standardization and efficient control ofprovisioning within a shared infrastructure model. Compared to a manual process that requirescoordination among different teams across a data center or IT organization, Matrix enables

administrators to provision an entire infrastructure service in just minutes or hours instead of weeks ormonths. Administrators can also continuously monitor and optimize the infrastructurefor example,by moving workloads or adjusting infrastructure service lease periodsas well as protect servicecontinuity with disaster recovery and automated server failover.

4


5/28

Figure 2: Conceptual diagram of the infrastructure orchestration capabilities of BladeSystem Matrix

Important terms

AllocationThe process of assigning server, storage, and network resources to a service requestbased on the criteria defined in the template, the resource pools assigned to the user, and thecurrent reservations or allocations of resources completed by the Matrix infrastructure orchestrationsoftware.

ApprovalsRequired for service requests submitted by self-service users, approvals are handledby an administrator, and occur between the allocation and provisioning phases of a service.

Infrastructure orchestrationThe set of processes, enabled by Matrix software, for designing,provisioning, and managing infrastructure services. The infrastructure orchestration software ofMatrix defines and enables three distinct roles:ArchitectUses the infrastructure orchestration graphical design tool to develop, test, andpublish service templates that capture the requirements to provision infrastructure services. Thearchitect specifies attributes for the logical resources, and may author and attach workflows toautomate additional IT tasks during provisioning or ongoing management of the serviceinfrastructure.

AdministratorUses the infrastructure orchestration console to create pools of servers andstorage, to manage the available networks and software inventory, to approve user requests, and

5


6/28

6

to modify user service infrastructures. The administrator may also perform manual tasks within asemi-automated operation.

UserUses the infrastructure orchestration self-service portal to request infrastructure services byselecting a service template, selecting one or more assigned resource pools to use, andspecifying a lease period for the start and end of the overall service. During the lease period theuser can update the service.

Infrastructure serviceA running configuration of infrastructure resources that is designed to

support a business application such as a multi-tier web application. Infrastructure resources includeserver blades, virtual machines, SAN disks, networks, and IP addresses. It is also referred to as aservice or service instance. Matrix provides lifecycle management of a service, including start andend controls, ability to extend service period and accompanying resource allocation, or addingserver or storage resources per template definition.

Lease periodThe duration, or lifetime, of an infrastructure service. It is set or changed by theuser.

Logical serverA management abstraction defined by a server profile that describes the systemresources needed for a given operating system (OS), application, and workload to operate. Forexample, a profile includes resource specifications such as processors and memory, and uniqueidentifiers such as Media Access Control (MAC) addresses and World-Wide Names (WWNs). A

logical server profile can be created for a physical server or a virtual machine and moved acrossphysical or virtual machines. Logical servers allow administrators to manage physical and virtualmachines using the same management construct. (For more information on logical servers, seeIntroducing logical servers: Making data center infrastructures more adaptive,http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01402013/c01402013.pdf.)

ProvisioningThe process of creating an infrastructure service from a template. The Matrixsoftware searches its inventory before allocating the infrastructure resources to all logical resourcedefinitions in the template.

Resource poolsA group of physical and virtual infrastructure resources. An administratorcontrols resource utilization by allowing users access to one or more resource pools.

Server groupDefined in a template, a set of one or more servers with the same role that can be

treated as a tier, enabling the construction of a multi-tier infrastructure service.Service requestSubmitted by a user to perform initial provisioning and ongoing changes to theinfrastructure. Users can monitor and cancel requests. Requests can be approved, rejected,canceled, or continued by administrators.

Service templateA design blueprint that specifies the requirements for an infrastructure servicein terms of server groups, networks, and storage, and contains customization points that useworkflows during the execution of a request.

WorkflowDefines a set of additional actions that execute customer-specific IT tasks. Workflowscan define integration with IT processes, including approvals, manual OS deployment, manualstorage provisioning, and sending notifications. Workflows can be associated with templates, to beexecuted before and/or after provisioning based on the associated templates. Examples include

workflows to update a configuration management database (CMDB) or open a change request in aticketing system at precise points within the provisioning or other infrastructure service lifecycleworkflow.

How BladeSystem Matrix is used

Perhaps the best way to understand the unique value of BladeSystem Matrix is to examine howcustomers can deliver and operate infrastructure services using Matrix. This section describes how IT
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01402013/c01402013.pdfhttp://h20000.www2.hp.com/bc/docs/support/SupportManual/c01402013/c01402013.pdf


7/28

7

staff can provision infrastructure services, optimize the infrastructure resources, and protect continuityof services.

Provisioning workloads in a shared services infrastructure

The most powerful attribute of the resources in BladeSystem Matrix is the speed and simplicity withwhich they can be carved up, and flexibly configured and reconfigured to match nearly anyapplications infrastructure requirements. Instead of having multiple different server configurations tomatch the varied CPU, memory, network, and storage requirements of the business applications, asingle Matrix environment can be used instead.

In a traditional IT environment, the deployment of a new application requires the involvement of manypeople and a high degree of coordination among them. An IT architect might draw up a designspecifying the servers, virtual machines, storage, and networks needed to support the application,and the connections between them, adhering to established policies and standards. Based on thisdesign, the different IT staff responsible for servers, storage, virtualization, networking, and facilitieswould assemble and/or activate the needed resources. This could take multiple weeks and involverepeated communication between the different IT groups.

Making use of role-based infrastructure orchestration software, Matrix enables:

Administrators to create pools of resources and oversee and control their use. IT architects to design the infrastructure to support business applications and publish service

templates to drive implementation.

Users of IT services to select from a catalog of service templates and request infrastructure services.The Matrix software simplifies, streamlines, and coordinates these processes, and automates theprovisioning of the infrastructure resources to satisfy approved requests.

Creating resource pools

An administrator can use the management console to define pools of server, network, and storageresources, register user accounts and assign resource pools to users (Figure 3). Through the console,the administrator can also define virtual machine images and software deployment jobs.


8/28

Figure 3: Creating server pools

Populating storage pools

The Matrix capabilities enable the Matrix administrator (typically a server administrator) to define thestorage needs of a physical or virtual server (for example, a boot disk of a specific size, a shareddata disk, and a private transaction log disk). A storage administrator can create and publish to astorage catalog in which storage administrators populate a set of storage volumes to meet theprovisioning needs of service templates in Matrix. The storage administrator controls the visibility of

the storage volumes and what operations can be performed. For example, the administrators couldallow changes in OS mode or adjustments in LUN (logical unit number) masking for some volumes.

When defining servers storage needs in Matrix, the Matrix administrator can request candidatematches from the storage catalog, and browse volumes chosen based on size, OS support, specifiedtags, and other values. The storage catalog also serves as a formal, automated communicationmechanism between Matrix administrators and storage administrators. Rather than having tomanually communicate storage needs to the storage administrator and later manually enter theinformation, the server administrator can request candidates through Matrix. If no matches are found,the storage administrator can see the unfilled request and provision appropriate storage (in otherwords, create the volume, present the volume, and adjust the SAN zoning, if necessary). The results ofthe storage administrators actions are automatically shown the next time the server administrator

requests matches.When paired with the HP StorageWorks EVA solution, the storage catalog in Matrix canautomatically discover existing volumes and enable the storage administrator to import them into thestorage catalog and assign authorizations, thus avoiding manual entry. Volumes created in otherStorageWorks and even third party SAN arrays can also be loaded into the storage catalog;additionally, the storage catalog can represent volumes from multiple arrays in the same catalog.

For customers wanting to integrate with their own storage provisioning processes, whether automatedor manual, there is command line access to the storage definitions (requests) and the ability to importresults back into the Matrix storage definitions.

8


9/28

Designing the infrastructure and creating templates

The architect uses a graphical designer (shown in Figure 4) to plan and design infrastructures to fit theneeds of business applications. By dragging and dropping and connecting icons representing therequired resources, the architect creates a template, saved as an XML file, for an infrastructureservice. These template files can also be imported and exported. The architect specifies attributes forthe logical resources, such as minimum memory required, IP address allocation, requirements forphysical or virtual servers, the amount of storage needed, and the software required on the boot disk.The architect saves each service template to a catalog for access only by specified, approved users.

The infrastructure orchestration software validates the design and presents information about anyissues so that they can be resolved before the template is published.

Figure 4: Creating a template using the graphical designer

The Matrix designer interface enables the architect to: Design for a range of application needs. The infrastructure service templates could be for a simple

virtual machine cluster for a web front end, a configuration for a test and developmentorganization, or it could be a complex, multi-tier configuration for an e-shopping application or anenterprise resource planning (ERP) or customer relationship management (CRM) implementation.

Incorporate established IT policies and standards with assurance that they will be followed in theprovisioning process.

Specify costs to support budget tracking and reporting.Attach custom workflows that automate key pre- and post-provisioning tasks.

9


10/28

Use workflows and processes to enable smooth transitions between roles or teams (Figure 5).Example workflows: Open Request For Change (RFC) tickets for requests in ticketing/ change management systems Pass customer, cost, and lease duration into a chargeback systemApply patching and compliance policies in configuration management tools Maintain status in change management systems as new services are created or changed

Design from scratch, modify previously created templates, or leverage best-practice templates. HPhas developed standard templates, working with key independent software vendors (ISVs), forapplications such as Microsoft Exchange, Oracle, and SAP, and others(www.hp.com/go/matrixtemplates).

Figure 5: Adding workflows

Requesting infrastructure services

An approved user can initiate the creation of a new infrastructure service from the publishedtemplates. Through the self-service portal, the user can:

Select a service template from the catalog (example in Figure 6). Users are able to browse thetemplates which they are authorized to use.

Select one or more assigned resource pools.View associated costs for the service and specify a lease period.The self-service portal displays all of the users service requests, with their status, and provides emailnotification when a status changes.

10
http://www.hp.com/go/matrixtemplateshttp://www.hp.com/go/matrixtemplates


11/28

Figure 6: Template catalog in self-service portal

Approval and provisioning

The Matrix software sends an email notification of pending service requests to the administrator.Through the management console, the administrator can review each request, and approve or deny

the request. Approval of a request initiates the provisioning process.To the infrastructure orchestration software, the components of each service template are logicalobjects. A key capability of the software is allocationthe process of finding the resources that matchthe logical objects. After a service request is submitted through the self-service portal, the Matrixsoftware validates the arguments for the service request and performs an allocation. If the resourcesthat match the template can be located, then the allocation is successful; the selected resources arereserved and provisioning proceeds.

Matrix performs automated provisioning for both virtual and physical servers, including physicalservers and virtual machine configurations, SAN disk support, OS deployment, and OScustomization. Matrix supports a variety of mechanisms for deploying OS software. The softwaresource can be virtual machine templates or HP server deployment software. When provisioning

several virtual machines from the same virtual machine template, Matrix can utilize linked clones,which speeds up the provisioning process and reduces the amount of storage required. Matrix alsosupports automated installation of application software through integration with HP Server Automationsoftware.

During provisioning, the Matrix orchestration software invokes any associated workflows at theirrespective execution points. Because the provisioning is automated and controlled by the template,administrators can enforce established standards and avoid variances due to human error.

11


12/28

12

Managing provisioned services

Both the administrator and the user who requested the service are notified when provisioning iscomplete. The administrator can view status, progress, and details of all completed and executingrequests and take action to resolve failed requests. The administrator can also modify serviceinfrastructures as required; for example, migrating workloads between server blades to supportproactive maintenance activities in the physical environment.

The provisioned service is available to the user for the duration of the specified lease period. A usercan manage provisioned services through the self-service portalsetting the servers to standby to

reduce power consumption if a service is not needed temporarily, resuming the service andreactivating the servers when needed again. The user can also easily request a modified service leaseperiod or request additional servers or storage. When a service is no longer needed, the user candelete it to make resources available for other purposes. Administrators can choose one of threeoptions for a service at the end of its lease period: ignore the service lease end and notify the user,suspend the service, or delete the service.

Continuously optimizing the infrastructure with capacity and powermanagement

Integrated capacity and power management capabilities keep infrastructure services provisioned in

HP BladeSystem Matrix running optimally. Built-in technologies throttle resources when not needed,keeping power consumption in line with actual server utilization. Dynamic power saver features canplace power supplies in standby to keep power supply efficiencies above 90% for all normaloperating conditions. As energy costs continue to rise, power consumption is an increasinglyimportant consideration when planning for server consolidations or growth.

Ongoing capacity management

Matrix enables administrators to quickly rebalance and repurpose physical and virtual servers toaddress changing business priorities. Using the integrated real-time capacity planning and workloadbalancing capabilities of Matrix, administrators can easily accommodate the varying resourcerequirements of an application workload. For example, varying the resources based on time of themonth when peak use increases dramatically during end-of-month processing or a sales promotion.

The capacity planning capability of Matrix measures the traditional resource metrics of CPU, memory,networking, and disk I/O, as well as power consumption, based on data collected every five minutesfor the Matrix server blades. In the management console, administrators can view both currentutilization and historical data by the type of resource. When resource utilization is low for a set ofphysical or virtual servers, administrators can evaluate consolidation alternatives using consolidationplanning scenarios.

It is helpful to understand the Matrix approach to analyzing capacity requirements, which is moresophisticated than simply determining the maximum memory or CPU utilization. A common practice incapacity planning is to simply take the peak of the two loads and use that to determine the maximumrequired capacity; this is the sum of peaks method. While this will provide a robust solution, this

method does not take into account the timing of the peak of the loads and may end up planning formore capacity than is actually used. A more efficient planning solution, referred to as the peak ofsums and easily accomplished with Matrix, takes into account the timing of the maximum utilizationpeaks in the individual loads. By adding together utilization at each measured interval and thentaking the maximum of the resulting time sequence, the peak of sums method used by Matrix resultsin a more accurate measure of the required maximum resource, thus reducing costs.

Consolidation planning with what-if scenarios

When planning for consolidation, an IT administrator can simulate the placement of server workloadsbefore they are implemented and compare resources used under multiple scenarios, taking into


13/28

account future trends. By analyzing these planning scenarios the administrator can determine optimalworkload placement.

With the Matrix scenario editor, the administrator can create a baseline scenario based on anexisting solution, and then generate the desired number of alternative scenarios for comparison. Foreach of the alternatives, the administrator can apply what-if actions, for example, automated systemconsolidation to virtual machines; specify configuration parameters; and include growth projectionsfor CPU, memory, disk I/O, and networking I/O, as well as utilization limits for each of theseresources. The capacity planner compares the alternatives and provides a recommended solution,

including a 5-star headroom rating and projected utilization. The administrator can then run acomparison report to determine possible outcomes. For example, administrators can compare relativeimprovement in power consumption from various alternative scenarios, as illustrated in Figure 7.Details of the consolidation scenarios give the administrator additional relevant data on which to basea decision regarding the best consolidation solution. The workload(s) can then be moved to theselected host, and the server blade freed up for other applications or powered down to save energy.

Figure 7: Consolidation planning scenario comparison report

Advanced power management: dynamic power capping

The dynamic power capping feature of Matrix safely limits peak power consumption withoutimpacting system performance and without risk of over-subscribing data center branch circuits. Thiscapability is enabled for every ProLiant server blade and blade enclosure. Administrators can setpower caps for individual server blades, for groups of blades or for an entire enclosure. Embeddedmanagement and power microprocessors on each blade work together both to measure and controlpower usage. When enforcing the user-defined power cap, the power microprocessor first will lower

13


14/28

14

the CPU P-state. If the required reduction in power has not been reached, it will continue to reduceCPU clock speed to prevent peak power consumption from exceeding the cap.

When applied at the enclosure level, dynamic power capping spreads the administrator-defined capacross multiple servers, dynamically adjusting the power caps for individual server blades, based onworkload intensity. Server blades running lighter workloads will have their power caps reduced;server blades running more intense workloads will have their power caps increased. Since workloadintensity will peak and subside at different times in most environments, the ability to adjust powercaps dynamically lets IT administrators set the enclosure-level dynamic power cap below the sum of

peak power consumption for each blade without impacting blade performance.

Protecting continuity of services using built-in disaster recoverycapabilities

Like all BladeSystem environments, BladeSystem Matrix is built with redundant components, so thefailure of a single component such as a power supply or fan does not impact operations. Matrix alsohas a server failover feature: if a server fails, the application can be restarted on a spare server, andthus be running again in about the time it takes to power on another server blade, boot the OS (whichresides on shared storage), and start the application service. Failover can take place within anenclosure, within a data center, or between data centers. This requires no special software to be run

on the servers, and spare servers can be pooled, so the total number of spare servers can be less thanthe number of protected operational servers.

Disaster recovery

Disaster recovery (DR) is licensed in every BladeSystem Matrix and can be enabled when combinedwith HP StorageWorks EVA or HP StorageWorks XP disk arrays with Continuous Access. The DRfunction provides for automated disaster recovery to a recovery site and failback, enabling transfer ofworkloads that run on physical servers or in virtual machines, or transfer from physical to virtual. Thelocation of the recovery site can be at a metropolitan-distance (up to 200 km) from the data center, orwith StorageWorks XP arrays, it can be located at a continental-distance (beyond 200 km). TheContinuous Access capabilities ensure that application data is properly transitioned to the recoverylocation, storage access is restored, and that the overall transition is executed in minutes, not days.

Enabling technology

BladeSystem c-Class

In designing the HP BladeSystem architecture, HP worked very closely with its customers to understandtheir requirements and challenges in managing their data centers. The resulting BladeSystem c-Classdesign incorporates modular and flexible compute, network, and storage resources to provide ageneral-purpose infrastructure that can accommodate continually changing business needs. As such,BladeSystem c-Class provides an ideal starting point for the BladeSystem Matrix solution.

Key components of this architecture include:

Embedded management: Included are Onboard Administrator management controllers at theenclosure level and Integrated Lights Out (iLO) intelligent management processors on every serverblade.

Onboard Administrator and iLO provide intelligence throughout the infrastructure to monitorpower and thermal conditions, ensure correct hardware configurations, simplify enclosure setup,and simplify network configuration.

The Onboard Administrator controller communicates with the iLO management processors oneach server blade and collects and manages system parameters related to thermal and powerstatus, system configuration, and managed network configuration. The iLO for BladeSystem


15/28

15

processor provides complete remote server virtual presence, including graphical remote console,virtual media, and more.

Shared cooling and power: HP consolidated power and cooling resources to conserve power andprovide efficient cooling, while efficiently sharing and managing the resources within the enclosure.HP uses the term Thermal Logic to refer to the mechanical features and control capabilitiesthroughout the BladeSystem c-Class that enable IT administrators to optimize their power andthermal environments.

High-performance, high-efficiency Active Cool fans provide redundant cooling across eachenclosure. These hot-pluggable fans are controlled by the Onboard Administrator so that coolingcapacity can be ramped up or down based on the needs of the entire system.

Onboard Administrator allocates power to the device bays based on the specific configuration ofeach blade in the enclosure. As blades are inserted into the enclosure, the Onboard

Administrator discovers each blade and allocates power accordingly, based on actual measuredpower requirements.

Virtualized connectivity: HP Virtual Connect technology provides a way to virtualize the server I/Oconnections to Ethernet and Fibre Channel networks.

For additional background on HP BladeSystem technologies see the following technology briefs: HPBladeSystem c-Class architectureand Technologies in HP ProLiant c-Class server blades at

http://h18004.www1.hp.com/products/blades/components/c-class-tech-function.html.

Virtual Connect

Virtual Connect is an essential foundation element in BladeSystem Matrix. Inherent in Matrixfunctionality and the powerful automation capabilities of its operations is the ability to moveworkloads from one server to another without human intervention or coordination, and VirtualConnect enables this.

Most LAN and SAN networks rely on the unique addresses of NICs and host bus adapters (HBAs)within each server. If a server is replaced, then the MAC addresses and WWNs associated withnetwork adapters and HBAs on the server change and the LANs and SANs attached to those serversneed to be adjusted. As a result, even routine server changes are often subject to delays for

coordination among IT operations groups.Virtual Connect brings all of the necessary capabilities into the domain of the system administrator.Virtual Connect adds an abstraction layer between the servers and the networks. It assigns and holdsall MAC addresses and WWNs at the server bay, instead of on the servers themselves. When a newserver is added, its NICs inherit their assigned MAC addresses and the HBAs inherit their WWNs.Similarly, when a server is removed, its replacement is assigned the same addresses so that the LANsand SANs dont see server changes and dont need to be updated for them. Using the local VirtualConnect Manager, or the data-center-wide HP Virtual Connect Enterprise Manager software, thesystem administrator can provision and pre-assign all of the LANs and SANs that the server poolmight ever need (from those pre-defined by the network and storage administrators) -- even before anyservers are installed. SAN and LAN administrators retain sufficient control over their domains but are

freed from interruptions for routine server maintenance.Through an extension of the same mechanism, Virtual Connect server connection profiles are assignedfor each server and these profiles can be moved from one server bay to another with a single mouseclick, within seconds. When combined with Boot-from-SAN and the Virtual Connect managementtools, application workloads can be moved from one server to another very quickly, securely, andautomatically and with their storage and network configurations intact. The application users areunaware of the change, as the OS image and data reside on shared storage accessible from a poolof servers. Figure 8 compares HP Virtual Connect to the traditional network model.
http://h18004.www1.hp.com/products/blades/components/c-class-tech-function.htmlhttp://h18004.www1.hp.com/products/blades/components/c-class-tech-function.html


16/28

Figure 8: Comparison of HP Virtual Connect to traditional model

Virtual Connect Flex-10 technology further optimizes networks by allowing administrators to divide asingle 10 Gb network connection into four independent FlexNIC server connections, reducingequipment needs by up to 75 percent. Administrators can dynamically adjust the bandwidth for eachFlexNIC connection in increments of 100 Mb between 100 Mb and 10 Gb.

HP Virtual Connect architecture uses industry standard Ethernet and Fibre Channel for simpleintegration with familiar brands, such as Brocade, Cisco, and ProCurve. The Virtual Connectarchitecture is built into every HP BladeSystem enclosure taking advantage of the high performance

interconnect channels, integrated I/O connections, Onboard Administrator communication andcontrol channels, and modular interconnect bays delivered as standard with HP BladeSystem. (Moreinformation on HP Virtual Connect technology is available at www.hp.com/go/virtualconnect.)

HP FlexFabric, built on Virtual Connect and ProCurve innovation, will enable network connections andcapacity to be fully virtualized from the edge to the core, enabling IT to deliver network-as-a service,wire connections once and to freely move applications across or between servers or even across orbetween data centers.

HP is committed to serving the diverse needs of modern data centers without imposing a specificoperating model, proprietary architecture, or network fabric. HP is continuing to build out theConverged Infrastructure vision with the addition of storage network protocols to its Virtual ConnectFlex-10 technology. This combines the capabilities of Virtual Connect and Flex-10 with ConvergedEnhanced Ethernet (CEE), Fibre Channel over Ethernet (FCoE), and accelerated iSCSI technologies toenable BladeSystem customers to use a single Virtual Connect server connection to access storageand server networks.

Ultimately, the HP goal is to allow IT to plug new systems into a Converged Infrastructure that willautomatically discover capacity, add it to resource pools, and put it to work to support the needs ofbusiness applications. For more information on HP FlexFabric, seehttp://h18004.www1.hp.com/products/solutions/converged/flexfabric.html.

16
http://www.hp.com/go/virtualconnecthttp://h18004.www1.hp.com/products/solutions/converged/flexfabric.htmlhttp://h18004.www1.hp.com/products/solutions/converged/flexfabric.htmlhttp://www.hp.com/go/virtualconnect


17/28

Storage technologies

Key to the flexibility of the Matrix solution is having the OS image and data reside on shared storage.Logical servers can then migrate from one physical server to another and retain their personality, andcontinue to provide application support after reboot. For physical servers, Matrix supports pre-provisioned Fibre Channel storage. Matrix can be connected to a customers existing SAN or Matrixcan be ordered with a factory integrated HP StorageWorks array such as the 4400 Enterprise Virtual

Array (EVA4400) storage solution.

Integrated management through Insight Dynamics software

As described in the section How BladeSystem Matrix is used, HP Insight Dynamics provides anintegrated toolkit for Matrix that enables the capabilities for delivering and operating infrastructureservices:

Visual design and automated provisioning of infrastructure services Infrastructure optimization through advanced capacity and power management and consolidation

planning

Protection of service continuity with integrated recovery managementThe home page for Matrix or Insight Dynamics 6.0, shown in Figure 9, gives users a full view andeasy access to the functions available.

Figure 9: Insight Dynamics 6.0 home page displays the full range of integrated functionality for Matrix

HP Insight Dynamics enables administrators to manage standalone physical servers, virtual machinehosts and guests, and physical hardware partitions on Integrity servers, all from a single managementconsole. Insight Dynamics also enables both physical blade servers and virtual machines to bemanaged as logical servers so they can be easily moved and migrated within a Matrix environment. Itdelivers a full range of deployment, management, capacity planning, migration, and movementcapabilities.

HP Insight Dynamics incorporates virtualization management built on years of experience with HPIntegrity systems combined with expertise in integrated management with key virtualization partners,

17


18/28

18

VMware and Microsoft. It gives IT administrators a unified method to manage both VMware ESX andWindows Server 2008 Hyper-V virtualization technologies, through API (application programminginterface) integration with tools such as VMware vCenter, vSphere, and vMotion, and with MicrosoftSystem Center. The combined HP and partner capabilities provide robust lifecycle managementofvirtual environments, including automated deployment, migration, capacity and power management,health monitoring, and disaster recovery. For example, when the Insight Software receives a ProLiantpre-failure hardware alert, it works with VMware vCenter to initiate the movement of all the virtualmachines on that server before the failure occurs.

Insight Dynamics builds on other proven HP technologies as well. Key examples of this include:

The infrastructure orchestration of Matrix that provides role-based design and provisioning includesan embedded workflow automation engine powered by HP Operations Orchestration software. Thisenables integration with customer IT processes and extensible automation using customerworkflows. (See Table 1 for a comparison of Matrix infrastructure orchestration and HP OperationsOrchestration software.)

Insight Dynamics seamlessly plugs into HP Systems Insight Manager (HP SIM) and leverages HP SIMadministration and infrastructure management facilities.

The integrated Storage Provisioning Manager facilitates interactions between server and storageadministrators, providing a consistent view of storage pools. The storage administrator retainscontrol of the storage catalog, storage-related processes, and permissions. The shared interfacemakes it simple for the server administrator to request needed storage and to see changes initiatedby the storage administrator.

For automated installation during service provisioning, Insight Dynamics supports the use of HPInsight Control server deployment for Windows and Linux OS, as well as VMware and Microsofthypervisors, and HP Ignite-UX to deploy HP-UX images. Simple integration steps enable InsightDynamics to also use HP Server Automation for automated deployment of the application, as wellas the OS.

Insight Dynamics links with HP Serviceguard software to provide mission-critical level highavailability and disaster recovery solutions for Integrity servers.


19/28

19

Table 1. Comparison of HP BladeSystem Matrix infrastructure orchestration and HP Operations Orchestration

Matrix orchestration Full-featured HP OperationsOrchestration

Purpose Automate pre/post Matrix orchestratedprovisioning tasks (such as open/closeticket, add to/remove from loadbalancer)

Integrates with HP and third-party systemsmanagement tools in support of Matrixorchestration processes such as ticketing*

Automate routine IT operational taskssuch as repetitive maintenance, changeexecution and incident resolution

Integrates with HP and third-party systemmanagement tools in support ofprocesses such as ticketing andmonitoring

Supported Devices Only Matrix managed devices: HPBladeSystem servers and x86-basedvirtual machines

HP and third-party servers, network,storage, and client devices

Included Workflowsand Integrations

Pre-defined workflows and operationsthat support Matrix capabilities andprotocols

Integration to HP management tools*

Operations Orchestration Studio to editor create new workflows*

3,000+ workflows, operations andintegrations for most industry-leadingoperating systems, databases,applications, and IT systems managementools

Workflow Execution Automatically triggered by Matrixorchestration actions (no userintervention)

Runs with or without user intervention, inresponse to an event, ad-hoc, or at pre-scheduled intervals

Scale and UserLicenses Included

One instance of embedded HPOperations Orchestration

One author license for workflow creation

Supports multiple clustered instances

Requires purchase of licenses for numberof authors and users needed

Reporting None Full reporting capabilities

*Additional HP or third-party licenses and/or services required

HP Insight Dynamics combines with HP Business Technology Optimization (BTO) software to enablemanagement of the broader IT environment. HP Server Automation software, part of the BTOportfolio, provides automated, server lifecycle management for heterogeneous enterprise servers andapplications, including full stack provisioning, configuration and compliance management.

Additional resources on Insight software can be found at www.hp.com/go/insightsoftware.

Integrating Matrix into customer environments

Because it is a standards-based solution, BladeSystem Matrix integrates with existing environmentsnetworks, SANs, applications, operating systems, and hypervisors.

Compatible with existing networks

Matrix connects seamlessly to existing Ethernet networks. Because Virtual Connect is a layer-2 bridge,not a layer-3 switch, it fits underneath any existing network. HP Virtual Connect Flex-10 interoperateswith any industry standard Ethernet switch while providing 4-to-1 network hardware consolidation ofthe server NICs and interconnect modules.

Compatible with existing SANs

The HP Virtual Connect 8 Gb interconnect is fully compatible with all standard NPIV Fibre Channelswitches, yet with more bandwidth and uplink capacity. The shared storage for logical server bootand data disks can be any pre-presented Fibre Channel LUN, although there are additional
http://www.hp.com/go/insightsoftwarehttp://www.hp.com/go/insightsoftware


20/28

20

capabilities with HP StorageWorks solutions, such as validation of the storage definitions and theability to import discovered volumes into the storage catalog.

Support for most common operating systems and hypervisors

Matrix supports these native server operating systems: Microsoft Windows Server, HP-UX, Red HatEnterprise Linux (RHEL), and Novell SUSE Linux Enterprise Server (SLES).

Matrix supports VMware ESX and Microsoft Windows Server 2008 Hyper-V hypervisors; withmanagement support for the Integrity Virtual Machines (orchestration support for Integrity VM is

planned).

For the latest and most complete information on BladeSystem Matrix compatibility, seewww.hp.com/go/matrixcompatibility.

Best practice application templates

HP has collaborated with key industry-vertical and infrastructure software partners to deliver bestpractice reference architecture templates, along with supporting solution guidance. These templatesdrop into the Matrix designer interface to provide a starting point for creating customer-readyinfrastructure service templates. IT architects can customize these templates to meet their specificinfrastructure requirements, and then proof them in test and development environments beforereleasing them for production use.

HP provides best practice white papers, sample workflows, and other guides along with the templatesto help customers get the most from the HP BladeSystem Matrix solution. Matrix ISV ApplicationTemplates available as of the publication of this paper include:

Microsoft Exchange Server 2007 and 2010 Microsoft Office SharePoint Server 2007 Microsoft SQL Server 2008 Oracle Real Application Clusters Oracle PeopleSoft Oracle Database 11g SAP NetWeaverFor access to the most up-to-date templates and other resources available for download, seewww.hp.com/go/matrixtemplates.

Integration with enterprise management systems

Insight Software for Matrix management includes APIs for integrating with enterprise managementsystems like HP Software and those from Computer Associates and Tivoli.

Security

With the powerful capabilities to manipulate IT resources that BladeSystem Matrix provides,appropriate levels of security are imperative. The BladeSystem Matrix solution provides a consistentand integrated security management framework that can be flexibly configured to satisfy local sitesecurity policies, utilizing security mechanisms in individual components and security services acrossthe integrated solution. Numerous security mechanisms are supported, including identification andauthentication, access control, authorization and auditing, as well as use of secure practices such assecure communication protocols. The security provided by the BladeSystem Matrix solution includesmechanisms to:

Ensure the confidentiality and integrity of management communications.
http://www.hp.com/go/matrixtemplateshttp://www.hp.com/go/matrixtemplates


21/28

21

Log all actions which manipulate server instances in HP SIM and other audit log files. Provide separation of duties and role-based access control for provisioning and management.Matrix provides a great deal of flexibility for dividing administrative operations. This is achievedthrough restricting login access and authorizations. Matrix uses the core authentication servicesprovided by HP SIM, leveraging the underlying Windows infrastructure, including the Active Directoryinfrastructure if available. The Matrix solution provides authorization mechanisms that simplify theconfiguration and ongoing management of privileges for the various levels of users. For example,

different levels of access to the Matrix infrastructure orchestration capabilities can be specified forarchitects, administrators and users, based on their individual needs. The authorization mechanismprovides the specified user with the ability to perform actions for which he/she has privileges and thegraphical user interface will only display the tasks that are allowed for the current user. Similarly, theintegrated Storage Provisioning Manager solution enables a storage administrator to control thevisibility of pre-provisioned Fibre Channel LUNs in the storage catalog, as well as controlling whichstorage operations a given server administrator (or Active Directory group) can perform.

HP SIM also provides an audit facility that logs entries for tasks performed by all users, includingexecuted tasks, authorization modifications, and user login and logout. Among the methods Matrixemploys to ensure secure management communications are use of the SSL (Secure Socket Layer)transport protocol and the SSH (Secure Shell) network protocol, and HTTPS (HTTP Secure) for web-

based communications. For a detailed discussion of security in Matrix, see the HP ConvergedInfrastructure Solution Security for HP BladeSystem Matrixwhite paper,http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA2-8444ENW.pdf.

Purchase and delivery

Purchasing BladeSystem Matrix begins with ordering a Starter Kit (Figure 10), which includes theinfrastructure needed for a fully-working environment:

A fully-redundant c7000 enclosureVirtual Connect modules Insight software licenses to enable all of the advanced Matrix functionality for an enclosure fully

loaded with ProLiant server blades (up to 16 ProLiant half-height server blades)

Implementation servicesIntegrity server blades can be purchased with any Matrix order as well, and when purchased with HPUX 11i v3 VSE-OEs or DC-OE, it includes necessary management software licenses. In conjunctionwith the Starter Kit order, the customer specifies the number and type of server blades needed andorders additional management software licenses for any Integrity blades specified. Additional optionsthat may be ordered include a StorageWorks EVA4400 array and a specially configured ProLiantBL460c G6 to function as the required central management server (CMS).

The customer can scale the capacity of the Matrix infrastructure by ordering one or more ExpansionKits, either with the initial Matrix purchase or as needs grow.
http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA2-8444ENW.pdfhttp://h20195.www2.hp.com/V2/GetPDF.aspx/4AA2-8444ENW.pdf


22/28

Figure 10. Purchasing BladeSystem Matrix

All HP BladeSystem Matrix Starter and Expansion Kit orders include factory services to:

Configure, rack, and cable the infrastructure.Verify and update firmware for the entire solution being purchased (the BladeSystem Matrix kits

and the supported blades and options purchased with those kits) to the latest current BladeSystemMatrix firmware release set.

Coordinate hand-off to Technology Services (TS) or an 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. Implementation services includeintegrating the hardware to the customer environment; installation and configuration of the centralmanagement server and other required software; and BladeSystem Matrix solution orientation. Anoverview of the implementation process is provided in Figure 11.

22


23/28

Figure 11. Overview of implementation process

For details on ordering a Matrix solution and related services, seehttp://h18004.www1.hp.com/products/blades/components/matrix/how_to_buy.html.

Summary and conclusion

The HP Converged Infrastructure strategy moves away from a product-centric approach to a shared-services model. In this model, traditional technology silos of server, storage, and network resourcesare converged into pools of virtualized and integrated assets that can be shared by manyapplications, optimized, and managed as a service. HP is delivering a Converged Infrastructuresolution today in the HP BladeSystem Matrix.

BladeSystem Matrix makes use of the best of HP enterprise technologies, integrated and delivered tothe customer as a complete Converged Infrastructure platform. With integrated Insight software,Matrix provisions infrastructure services, from simple to complex, automatically, making themavailable to the business in minutes or hours rather than weeks or months. At the same time, Matrixincorporates established IT processes, enables IT personnel to maintain appropriate controls, and

23
http://h18004.www1.hp.com/products/blades/components/matrix/how_to_buy.htmlhttp://h18004.www1.hp.com/products/blades/components/matrix/how_to_buy.html


24/28

24

enforces IT standards. With built-in capacity planning, power management, workload balancing anddisaster recovery capabilities in Matrix, IT staff can confidently optimize infrastructure resources andprotect continuity of services.

HP BladeSystem Matrix accelerates delivery of IT services, simplifies ongoing infrastructuremanagement, and enables IT departments to respond flexibly and efficiently to dynamic businessconditions.


25/28

25

Appendix: Matrix use cases

Use case 1: Creating a service template for Microsoft ExchangeThe following example describes how a typical enterprise could benefit from HP BladeSystem Matrixto create a catalog of templates for provisioning infrastructure services. This example, based onindustry best practices, describes the design of a complex multi-tier service running MicrosoftExchange 2007 for 500 mailboxes. The resources for this service include:

Physical servers for Exchange mailbox serversVirtual machines for Exchange hub servers Public network connections Private heartbeat connection for the cluster nodes Storage resourcesTo derive customized requirements for a highly available and high performance service to support500 mailboxes, the architect uses the HP Sizing and Configuration Tool for Microsoft ExchangeServer 2007 (www.hp.com/go/activeanswers). The architect uses the import function of the Matrixdesigner tool to accelerate the design process by starting with an existing Matrix template forExchange (Figure A-1). Best practice templates for Matrix are available atwww.hp.com/go/matrixtemplates.

Using the ActiveAnswers configuration and sizing tool, the architect generates a recommendedconfiguration using the following requirements:

Number of Mailboxes: 500 Mailbox Size: 500 MBWorkload Definition: medium Preferred Server, Platform: Blade BL Series Processor: Intel Server: ProLiant BL460c Server Storage Architecture, select SAN Storage Fibre ChannelArray Choices: StorageWorks EVA4400 High Availability: Cluster Continuous Replication (CCR)The architect updates the imported base template for the Exchange service using the configurationdetails provided by the sizing tool, including the number of storage groups, the size of the storagegroup for the database and its transaction log, and the recommended RAID level. The architect namesand saves the newly customized template. Following similar steps, the architect can create a catalogof templates from which users can provision the infrastructure services needed.
http://www.hp.com/go/activeanswershttp://www.hp.com/go/matrixtemplateshttp://www.hp.com/go/matrixtemplateshttp://www.hp.com/go/activeanswers


26/28

Figure A-1. BladeSystem Matrix reference architecture infrastructure template for Microsoft Exchange service

Use case 2: Increasing availability of infrastructure services during

planned downtimeThis use case illustrates how an organization can increase availability of infrastructure services duringplanned or unplanned downtime by freely moving workloads between servers in Matrix. In this case,one of the Matrix servers, a ProLiant BL465c server blade running a mail and messaging application,needs a memory upgrade.

Using Insight Dynamics in Matrix, the server administrator:

Obtains system information for the server blade and observes the current utilization of the serverblade. By performing the move while the system load is low, the administrator minimizes impact onusers of the application.

Evaluates and selects a suitable target to accept the workload. Insight Dynamics displays availableserver blades. In this case, a BL465c and a BL460c are available. The BL460c has more headroom(indicated with a 5-star rating), but the BL465c has a 4-star headroom rating and is the same typeof server blade on which the mail application is currently running.

Initiates the move operation. The software deactivates the original server and moves its profile to theselected target blade. Within a few minutes, the mail and messaging workload is activated on thenew server.

Monitors the progress of the operation in real time. The administrator has the option to proceedwith other work, as no user interaction is required.

26


27/28

27

With the workload moved to the new server, the mail and messaging service remains available tousers with virtually no interruption. The administrator can commence the maintenance on the originalserver blade. Once the hardware maintenance is complete and the administrator identifies anappropriate time, a similar process can be used to move the workload to the upgraded server.

A step-by-step guide and demo video for this use case can be viewed at:http://h18004.www1.hp.com/products/blades/components/matrix/guides.html#ha.

Additional use cases

Dynamic infrastructure provisioningUsing Matrix, administrators can create a multi-tier test and development infrastructure using physicalservers and virtual servers. In this scenario, a team is responsible for developing and testing multipleversions of a supply chain database application service. This example includes an IT architectdesigning and publishing the service template, a member of the test team creating the service usingthe self-service portal, an administrator approving the pending request, and automated provisioningand management of the service.

Matrix can also be used to rapidly activate and deactivate test and development environments, toquickly repurpose infrastructure without reinstallation. Resources may be pooled and shared,improving utilization and reducing cost. A logical server can be created for each application test

environment; each logical server can be provisioned once and then, as priorities change, logicalservers not being used can be deactivated. A deactivated logical server does not consume serverresources such as CPU, memory, or power, but its profile, including associated SAN storage, isretained so that it can be quickly reactivated in about the same time as it takes to boot the operatingsystem.

Step-by-step guides and recorded demos documenting these two scenarios can be found athttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#di.

Continuous consolidationThe real-time capacity planning capability of Matrix enables rapid rebalancing and repurposing ofphysical and virtual servers to address changing business priorities. As resource requirements ofapplication workloads lessen, these workloads can be dynamically consolidated onto fewer virtualmachine hosts to allow for better utilization of the existing server blade hardware. Any physical serverblade no longer needed after the consolidation can either be temporarily powered off to save energycosts, or quickly and easily repurposed.

Two use cases illustrating this scenario have been documented in step-by-step guides and demovideos, one using VMware ESX virtual machines, and another using Microsoft Hyper-V virtualmachines. These guides and videos are available athttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#cc.

Energy-aware planningMatrix real-time capacity planning capabilities also enable consolidation of workloads in an energy-efficient manner. The use of capacity planning scenarios and scenario comparison reports makes it

easy to compare energy consumption of different data center configurations, enabling better use ofpower, cooling and space resources. Details on this use case are available in a step-by-step guideand recorded demo athttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#ea.
http://h18004.www1.hp.com/products/blades/components/matrix/guides.html#hahttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#dihttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#cchttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#eahttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#eahttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#cchttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#dihttp://h18004.www1.hp.com/products/blades/components/matrix/guides.html#ha


28/28

For more informationFor more information

For more information on HP BladeSystem Matrix see:For more information on HP BladeSystem Matrix see:

www.hp.com/go/matrixwww.hp.com/go/matrix

www.hp.com/go/matrixdemos

www.hp.com/go/matrixtemplates

www.hp.com/go/insightsoftware

www.hp.com/go/convergedinfrastructure

Technology for better business outcomes 2010 Hewlett-Packard Development Company, L.P. The information containedherein is subject to change without notice. The only warranties for HP products andservices are set forth in the express warranty statements accompanying suchproducts and services. Nothing herein should be construed as constituting anadditional warranty. HP shall not be liable for technical or editorial errors oromissions contained herein.

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

Linux is a U.S. registered trademark of Linus Torvalds.

Oracle is a registered US trademark of Oracle Corporation, Redwood City,California.

4AA0-5550ENW February 2010
http://www.hp.com/go/matrixhttp://www.hp.com/go/matrixhttp://www.hp.com/go/matrixdemoshttp://www.hp.com/go/matrixtemplateshttp://www.hp.com/go/insightsoftwarehttp://www.hp.com/go/convergedinfrastructurehttp://www.hp.com/go/convergedinfrastructurehttp://www.hp.com/go/insightsoftwarehttp://www.hp.com/go/matrixtemplateshttp://www.hp.com/go/matrixdemoshttp://www.hp.com/go/matrixhttp://www.hp.com/go/getconnected

Documents

Understanding the HP Blade System Matrix Technology