HP Server Best Practices Guide

7/24/2019 HP Server Best Practices Guide

1/34

HP SUM Best Practices Planning Guide

AbstractThis document describes the best practices for performing a firmware and software update for your server environment withHP SUM. This document is intended for individuals who perform updates and understand the configuration and operations ofMicrosoft Windows, Windows Server, Linux, smart components, and the risk of data loss from performing updates.

HP Part Number: 658524-006aPublished: December 2015Edition: 2


2/34

Copyright 2009, 2015 Hewlett-Packard Development Company, L.P.

Notices

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 l icense 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

vendors standard commercial license.Microsoft, Windows, Windows Server are trademarks of the Microsoft group of companies.


3/34

Contents

1 Introduction...............................................................................................5Overview................................................................................................................................5Explanation of guides...............................................................................................................5

2 Planning for server environment scenarios......................................................6

One or more servers in a single location......................................................................................6Updating a single BladeSystem enclosure....................................................................................7Distributed corporate customer...................................................................................................8Large data center.....................................................................................................................9CloudSystem and CloudSystem Matrix.......................................................................................11

Helion CloudSystem...........................................................................................................11CloudSystem Matrix...........................................................................................................11Services overview..............................................................................................................12

Updating mixed ProLiant and Integrity environments....................................................................12Performing the update overview...........................................................................................12

3 Planning maintenance and update best practices..........................................13

Best practices overview............................................................................................................13General deployment planning..................................................................................................13Server planning......................................................................................................................14BladeSystem enclosure and server planning...............................................................................14

VC firmware planning.............................................................................................................16ProLiant iLO planning..............................................................................................................16

4 Best practices to minimize downtime...........................................................17Downtime causes....................................................................................................................17Node-specific tips to reduce downtime......................................................................................17

OA..................................................................................................................................17Servers.............................................................................................................................17

Enclosures.........................................................................................................................18Installation method tips............................................................................................................18

5 Firmware and software deliverables............................................................19Release sets...........................................................................................................................19Service Pack for ProLiant..........................................................................................................19

SPP release naming............................................................................................................19Adding or removing components from SPP............................................................................19Downloading the SPP.........................................................................................................19

Integrity firmware bundles........................................................................................................20Downloading Integrity bundles............................................................................................20

Moonshot Component Pack......................................................................................................20

Downloading the Moonshot Component Pack........................................................................20Creating a custom ISO or baseline............................................................................................20

6 Update tools............................................................................................22HP SUM................................................................................................................................22HP SIM and Version Control Agent...........................................................................................23OneView...............................................................................................................................23

VCSU....................................................................................................................................24SCCM...................................................................................................................................25

VMware ESXi firmware updates................................................................................................25VMware ESXi 5.0 and later.................................................................................................25VMware ESXi 4.x and earlier..............................................................................................25

Contents 3


4/34

7 Collecting installed versions of data............................................................278 Support and other resources......................................................................28

Contacting HP........................................................................................................................28Related information.................................................................................................................28Typographic conventions.........................................................................................................29

9 Documentation feedback...........................................................................31Acronyms and abbreviations.........................................................................32Index.........................................................................................................34

4 Contents


5/34

1 Introduction

OverviewFirmware, software, and drivers for your server environment are crucial for maintaining serversystems. HP has created the update packages to help you maintain your servers as consistentlyand easily as possible. Planning for your updates helps make the process go smoothly and minimizes

downtime.This document offers best practice and update planning guidelines to help plan firmware, software,and driver updates to your environment.

Explanation of guidesThese guides are written to help you create strategies for using the HP SUM update packages.

HP SUM Best Practices Planning GuideProvides best practice and planning guidance forfirmware update tasks. These tasks include general tips and maintenance recommendations.

HP SUM Best Practices Implementation GuideProvides more specific scenario based examplesfor implementing updates various solution infrastructures. Use this document after using the

HP SUM Best Practices Planning Guideto plan an update.You can find these guides on the Information Library at http://www.hp.com/go/hpsum/documentation.

Overview 5
http://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentation


6/34

2 Planning for server environment scenarios

One or more servers in a single locationIf you have an environment where all the servers are in one physical location you can use one ofthe servers to run the server updates. You can also use a non-server workstation to run the serverupdates, and deploy updates to the other servers. Use the following instructions to gather the

information required to create a server update plan. For detailed instructions about performing theupdate, see the One or more servers in a single location section in theHP SUM Best PracticesImplementation Guide.

DescriptionItem

Workstation1

Server2

Download the update package you want to use, for example, SPP or Integrity bundle. Formore information on downloading the files, seeDownloading the SPP (page 19)orDownloading Integrity bundles (page 20).

NOTE: The SPP and Integrity bundles include a copy of HP SUM. You can download thelatest version of HP SUM from the HP SUM website at http://www.hp.com/go/hpsum.

Determine if you must create a custom ISO. For more information about creating a customISO, seeCreating a custom ISO or baseline (page 20).

Determine updates do you need to apply. Use HP SUM to do the following:

Create a baseline.

Add the nodes you want to update.

Inventory the nodes.

Generate theDeploy previewreport.

Review the updates for your server.

http://www.hp.com/go/hpsumhttp://www.hp.com/go/hpsum


7/34

Determine if the software updates or new features are items you need immediately, or if youcan wait for a regularly scheduled maintenance window to apply them.

Configure the firewall to allow remote support for HP SUM. You might need to enable trafficthat the remote server initiates. For more information, see theHP Smart Update Manager UserGuide.

For Windows servers, be sure that you enable file and print services. For Linux and HP-UXservers, be sure you turn on the SSH service.

In some cases, updating the iLO firmware separately helps decrease update duration.

Updating a single BladeSystem enclosureThis section covers the process to update a single c-Class enclosure with servers and associatedinterconnect modules.

DescriptionItem

Management server1

Server2Enclosure3

Storage4

Items to consider when creating an update strategy:

Determine the baseline to use for deployment.

Determine if you must create a custom ISO. If so, seeCreating a custom ISO or baseline(page 20)for more information.

Determine updates to apply. If so, use HP SUM to do the following:

Create a baseline.




Review the updates and hot fixes.


Updating a single BladeSystem enclosure 7


8/34

Consider methods to minimize business impact from updates. If an enclosure houses multipledepartments, look for ways to coordinate updates between different business units.

Run a health check to be sure your OA and VC firmware are ready for updates.

Distributed corporate customerThe distributed corporate customer has a central data center with servers at multiple remote locations.

DescriptionItem

Management server1

Server2

Enclosure3

Storage4

Remote servers5

Two remote servers, one remote storage6

Items to consider when creating your update strategy:

Determine if you are creating a custom ISO. If so, seeCreating a custom ISO or baseline(page 20)for more information.

Determine updates to deploy. Use HP SUM to do the following:

Create a baseline.




Review the updates and hot fixes for your environment.



9/34


Determine how you will distributing the updates.

Burn DVDs or create USB keys, and then send the physical media to each remote server.

Copy the files to remote servers.

Put the ISO contents on a central server and connect to it through network connections(network share in Windows or NFS mount in Linux).

Determine how you will perform the updates.

Install on each target individually.

Use PXE boot or iLO Virtual Media to install the SPP or Integrity bundle on servers overthe network.

Copy the SPP or Integrity bundle to one computer, and then write a script to install it onthe other local servers using HP SUM or iLO Virtual Media.

Consider methods to minimize business impact from updates. It might be necessary to perform

partial updates to enclosures if all servers cannot be taken out of service at once. Even whenpartial updates are required, follow the recommended installation order. For more information,seeBest practices to minimize downtime (page 17).

Determine if you will update an existing server automatically.

Determine if you have a lab environment set up. If you are creating your own ISO, be surethat you validate the solution before applying it to targets.

Determine if you have a backup of the server and the configuration of other targets.

Determine if you have the ports open to allow remote support for HP SUM.

In some instances, it might help decrease the time for the updates to complete if the iLOfirmware is updated independently of the other updates.

Large data centerThis section discusses updating a large data center that includes multiple enclosures, servers, andother components located in several locations.

Large data center 9


10/34

DescriptionItem

Storage1

Enclosure2

Management server3

Server4

The following list contains items to consider when creating your update strategy: Determine what firmware, software, and driver versions are you using on your servers. Run

HP SUM to create a report.

Create a baseline.



Generate theFirmware detailsreport.

Generate theDeploy previewreport to view available updates for the nodes.

Determine if you are creating a custom ISO. If so, seeCreating a custom ISO or baseline(page 20)for more information.

Determine how you group models in your data center. Group the same server models andtechnologies together in update groups. For example, group all ProLiant G5 servers together,and all ProLiant G1 servers together.

If you have multiple generations of servers in an enclosure, try not to mix servers that are morethan two generations apart in the same enclosure. For example, enclosures that include ProLiant



11/34

Gen8 and Gen9 server blades should not include ProLiant G6 server blades in them. Thethree main reasons for this are:

New generations of blades usually have more updates than older blade generations soupdating the enclosures where these older blade generations coexist can lead to extradowntime for these older server blades when the infrastructure is updated.

As servers age and the number of updates released are reduced, it is best to create abaseline for the servers at a given level of firmware and software and not update them

unless there is a need to re-provision them. This reduces the number of servers that needto be updated when a new baseline is introduced to the environment.

It helps minimize dependencies between different generations of servers that might affectthe success of the firmware update process.

Determine how do you deploy updates.

Verify that updates apply to your servers and targets.

The number of updates that support a server decreases over time. Check the updateinformation to be sure the firmware and software updates apply to your server generations.Most updates affect the latest generation.

Determine if you have third-party vendor equipment in your environment. If so, be sure thatupdates you apply are supported by HP and your third-party vendor.

Consider methods to minimize business impact from updates. Schedule any outages. It mightbe necessary to perform partial updates to enclosures if you cannot update all at once. Evenwhen partial updates are required, follow the installation order. For more information, seeBest practices to minimize downtime (page 17).

CloudSystem and CloudSystem Matrix

Helion CloudSystem

Helion CloudSystem operates with supported and current HyperVisors from third-party vendors.Driver deployment, firmware deployment, and implementation best practices are influenced anddictated by the same HyperVisor support processes per supported hardware/server platform.

For more information on Helion CloudSystem, seehttp://www.hp.com/go/cloudsystem.

CloudSystem MatrixCloudSystem Matrix, built on HP BladeSystem architecture, is a converged infrastructure platformfor shared services. CloudSystem Matrix delivers one virtualized pool of network, storage, andcomputer resources, that enables you to adjust to dynamic business demands by provisioning andmodifying a complex infrastructure in minutes rather than days, weeks, or even months.

CloudSystem Matrix combines automated design and provisioning through a self-service portalwith capacity planning and disaster recovery into a command center that unites your physical andvirtual worlds.

To assist you in setup, HP Services provides a three-step service to achieve full conversion:

1. Initial assessment.2. Site-specific preparation.3. Conversion to CloudSystem Matrix.

For more information, see the CloudSystem Matrix website at http://www.hp.com/go/matrix.

CloudSystem and CloudSystem Matrix 11
http://www.hp.com/go/cloudsystemhttp://www.hp.com/go/matrixhttp://www.hp.com/go/matrixhttp://www.hp.com/go/cloudsystem


12/34

Services overviewHP Services can help you optimize business results with consulting, outsourcing, and supportservices. For more information about services available, go to the Services website athttp://www.hp.com/services.

Updating mixed ProLiant and Integrity environmentsTo update an environment with both ProLiant and Integrity servers:

1. Review the support matrix. Be sure to use OA and VC versions supported by both ProLiantand Integrity servers. For more information, see the BladeSystem Release Sets for MixedProLiant and Integrity website athttp://h18004.www1.hpe.com/products/servers/firmware/mixed-release-sets.html.

2. Download the latest SPP version and Integrity Smart Update Firmware bundles.

NOTE: You can also use theCheck for Latest Updates from ftp.hp.com function in HP SUM.

3. Extract the SPP and Integrity Smart Update Firmware bundles to separate directories. Do notplace more than one bundle or SPP in a directory.

4. Launch HP SUM and on the Baseline Library screen, add the baselines.

NOTE: The SPP and Integrity bundles include a copy of HP SUM that will deploy thecomponents in that SPP or bundle. A newer version of HP SUM might be available. You candownload the latest version of HP SUM at http://www.hp.com/go/hpsum.

5. Perform your updates. Be sure you do not update the OA or VC to a version not listed in thesupport matrix.

Performing the update overview1. Download the SPP or the Integrity bundle. For more information, seeDownloading the SPP

(page 19)orDownloading Integrity bundles (page 20).

NOTE: HP SUM 7.1.0 and later supports online driver updates for VMware ESXi 5.x andlater.

2. Gather information about the servers and targets you want to update.a. Gather IP addresses for the OA, Virtual Connect Manager, iLO, and at least one NIC in

each server.b. For all VC modules, run the VCSU health check to determine if the VC modules are in a

good health state that allows firmware updates to proceed before updating any OA orVC modules.

c. Create a firmware report for the OA, Virtual Connect Manager, iLO, and server IPaddresses with HP SUM. You can use the GUI, CLI mode, Input file, or interactive CLI

mode. This report displays what is currently installed on the selected nodes.3. Perform the update. For update instructions, see theHP SUM Best Practices ImplementationGuide.

4. Review the results and logs from the update to ensure the update installed correctly.5. Use HP SUM to generate a report of the currently installed firmware to save for your records.

Compare the new report to the report you ran before performing the updates to see what youchanged.

http://www.hp.com/serviceshttp://www.hp.com/serviceshttp://h18004.www1.hpe.com/products/servers/firmware/mixed-release-sets.htmlhttp://h18004.www1.hpe.com/products/servers/firmware/mixed-release-sets.htmlhttp://www.hp.com/go/hpsumhttp://www.hp.com/go/hpsumhttp://h18004.www1.hpe.com/products/servers/firmware/mixed-release-sets.htmlhttp://h18004.www1.hpe.com/products/servers/firmware/mixed-release-sets.htmlhttp://www.hp.com/serviceshttp://www.hp.com/services


13/34


14/34

In some instances, it might help decrease the time for the updates to complete if the iLOfirmware is updated independently.

Test your environment in a lab before rolling into the production environment.

In CLI mode, use the/dryrunattribute to simulate an installation.

If you do not have a lab, choose one server to update and run the server for a few daysunder a normal workload. When the server proves stable, update the remaining servers

in your environment.

Server planning Backup the server before starting an update.

Use HP SUM to generate reports of firmware and software currently installed on targets. Usethe report to determine recommended updates for each target before deploying updates.

NOTE: Some updates require an offline update. For information on which updates requireoffline updates, see theSupport Pack for ProLiant Release Notes.

Deploy drivers concurrently with firmware updates to ensure dependencies are fulfilled.

If you must deploy firmware or software separately, use the following order:

Update drivers first.

Update additional software, such as agents and utilities.

Update the firmware.

Do not downgrade or rewrite firmware unless there is a specific need to do so.

NOTE: Downgrading firmware might cause incompatibilities between devices if thedowngraded firmware does not work well with other device firmware or drivers.

Reboot the server after server-based firmware, software, or driver upgrades. This clears thememory and allows the update component to start fresh.

Use a USB or network file share to add or remove software and firmware.

For new servers, update the firmware before installing the operating system. You might needto run the updates twice to install the most recent updates.

Test your environment in a lab before rolling into the production environment.

Use/dryrunfrom the command line in HP SUM to simulate an installation.

If you do not have a lab, choose one server to update and run the server for a few days

under a normal workload. When the server proves stable, update the remaining serversin your environment.

BladeSystem enclosure and server planning If possible, do not mix servers that include more than two generations difference in the same

enclosure. For example, if your enclosure includes ProLiant G6 and G7 servers, do not addProLiant Gen9 servers.

14 Planning maintenance and update best practices


15/34

NOTE: If you update enclosures that mix multiple generations, plan for more downtime forserver blades when you perform updates.

As servers age, fewer critical updates and hot fixes are released. Create a baseline with thefirmware, software, and drivers used for each server.

Ensure that the NIC firmware included in a release set is supported by the operating systemvendor and external network switch vendors before updating it. Review the following known

issues: A purple screen (PSOD) occurs on some 10GbE adapters. For more information, see the

customer advisory website at

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982

Updating Broadcom 1GbE drivers for Windows Servers requires first updating to version4.6.16.0. For more information, see the customer advisory website at


Emulex be2net Inbox Driver version 4.0.88.0 does not support Flex-10 or Flex FabricAdapters. For more information, see the customer advisory website at


NOTE: Some Broadcom firmware updates require you to update the driver and reboot thesystem to activate the driver before you can update the firmware.

Do not update servers unless you need to re-provision a server. This reduces the number ofservers you update when you introduce a new baseline.

HP Integrity and ProLiant servers might have different OA and VC firmware versionrequirements. For more information on mixing servers in one environment, seeUpdatingmixed ProLiant and Integrity environments (page 12).

Consider these known issues:ProLiant G2, G5, and G6 server ROMs dates May 2011 and later cannot be downgradedwithout using special steps. For more information, see the customer advisory website at


CPLD firmware for ProLiant G7 and earlier servers require you to physically remove thepower source for 30 seconds before an update activates.

Ensure that the FC HBA firmware included in a release set is supported by the external storagevendor before you update the FC HBA. For more information about comparing supportedHBA driver versions and storage devices, see the Single Point of Connectivity Knowledge

(SPOCK) website atwww.hp.com/storage/spock. Gen8 and Gen9 servers: Review theSPP Release Notesand VMware firmware recipe

documentation before creating a custom baseline or ISO to deploy updates. For moreinformation see:

http://www.hp.com/go/spp/documentation

http://vibsdepot.hp.com/hpq/recipes/

BladeSystem enclosure and server planning 15
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c01684544http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c03005737http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02838375http://www.hp.com/storage/spockhttp://www.hp.com/go/spp/documentationhttp://vibsdepot.hp.com/hpq/recipes/http://vibsdepot.hp.com/hpq/recipes/http://www.hp.com/go/spp/documentationhttp://www.hp.com/storage/spockhttp://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02838375http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c03005737http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c01684544http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982


16/34

VC firmware planning Check the compatibility matrix before you update an enclosure in mixed environments. For

more information, seeUpdating mixed ProLiant and Integrity environments (page 12).

Run a health check before you update OA or VC firmware.

Verify that firewall programs are not blocking VC firmware updates.

Be sure that you update profiles if you move blades around and between enclosures.

Review the latest VC release notes for any VC firmware release to determine any firmwareand driver changes needed for Ethernet, FC HBA, and CNA adapters in the servers. For moreinformation about Virtual Connect release notes, see the Virtual Connect website athttp://www.hp.com/go/vc/manuals.

General guidance does not mandate the use of either HP SUM over Virtual Connect SoftwareUtility (VCSU). See the following document on the HP website for more information whetherto use HP SUM or VCSU.


Be sure that the VC modules are set up in a redundant configuration.

Use VCSU to update modules that are not set up in a redundant configuration.

Monitor customer advisories for VC firmware update issues.

Validate the NICs and the FC HBA and CNA firmware and driver compatibility.

ProLiant iLO planning iLO 4 firmware, use version 2.03 or later. This resolves issues from previous iLO 4 versions.

iLO 3 firmware cannot be downgraded from version 1.25 to an earlier version without thedowngrade resetting some configuration data to the default value.

iLO 3 firmware 1.25 can cause a condition where the power is incorrectly reported and mightprevent some blades from powering on in a fully populated enclosure. Version 1.26 resolvedthis issue.

Event ID 57 errors are corrected for iLO 2 by using firmware version 1.82 or later and ProLiantiLO 2 Management Controller Driver for Windows 1.12.0.0 or later.

iLO 2 firmware 1.78 or later is required to update Power Management Controller firmware.

You cannot update iLO 2 firmware 2.00 through the iLO NIC Management interface.

Use iLO 2 firmware 1.81 or later to update CPLD firmware (ProLiant ML/DL300 series servers).

16 Planning maintenance and update best practices
http://www.hp.com/go/vc/manualshttp://www.hp.com/go/vc/manualshttp://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02885443http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02885443http://www.hp.com/go/vc/manualshttp://www.hp.com/go/vc/manuals


17/34

4 Best practices to minimize downtimeThe best practices mentioned here are recommendations that work for most environments. Modifyyour update plans based on your unique environment.

Downtime causesThe following items frequently cause downtime when you perform updates.

Driver installation requires a reboot to load the driver.

NOTE: You can deploy some updates online that immediately activate. The activation processmight cause a short network connectivity timeout. This might cause some applications that aresensitive to network connections to incur an issue. If you are using applications that are sensitiveto network disconnections, only deploy updates during regular maintenance windows.

Firmware updates require a reboot to activate the new firmware.

Firmware updates require exclusive access to hardware.

Dependencies between updates require offline deployment.

Hot fixes and customer advisories.

The method of installation.

Node-specific tips to reduce downtimeThe following tips help develop a server update plan that minimizes downtime.

OA

Before performing an OA update, perform a VC health check. If you update the OA whenthe VC is in an unhealthy state, you risk losing the network connection.

If using OA version 1.x, you must update to 2.32 before updating to newer versions.

Servers

Use a well-tested baseline, preferably the SPP or Integrity bundle.

Check for ProLiant hot fixes or Integrity bundles classified as critical or recommended thatapply to your systems.

Perform updates online using HP SUM or SIM first. This limits, or eliminates, the number ofupdates required in offline mode.

Perform infrastructure updates in parallel or prior to performing updates to servers.

Install the firmware and drivers together. This allows a single reboot to activate the maximumamount of updates.

If you are using iLO Virtual Media to deploy the updates, update iLO firmware through theiLO web GUI or scripting. For more information, see the iLO 4 User Guideor iLO 4 Scriptingand Command Line Guide, available at http://www.hp.com/go/ilo/docs.

Update HP-UX and iLO targets on Integrity racks or blade servers. Set HP SUM to performreboots to activate the new firmware automatically. HP SUM will order the updates so onlyone reboot is required to activate the firmware on both targets.

Update HP-UX running on nPartitions and partition firmware through the OA in the same HPSUM session. Set HP SUM to perform reboots to activate the new firmware automatically. HPSUM orders the updates and performs one reboot to activate the firmware on both targets.

Downtime causes 17
http://www.hp.com/go/ilo/docshttp://www.hp.com/go/ilo/docs


18/34

EnclosuresIf you are deploying updates through iLO vMedia in an enclosure, do not update more than 6-8blades at the same time.

Installation method tips Online updates enable you to stage multiple updates and reboot once to activate the updates.

NOTE: Some updates require an offline update. For more information, see theSupport Packfor ProLiant Release Notes.

Upgrade drivers and firmware at the same time. This minimizes problems that might occur ifthere are interdependencies between firmware and drivers.

The number of baselines you use and the number of nodes you update impact the systemresources the host system requires. The Input file mode requires fewer resources than GUImode.

Use HP SIM to deploy updates when you are updating more than 50 nodes concurrently.

New ProLiant hardware deployments require offline updates.

18 Best practices to minimize downtime


19/34

5 Firmware and software deliverables

Release setsRelease sets are collections of firmware, software, drivers, and other updates that are releasedtogether. SPP, Integrity bundles, and Moonshot Component packs are deliverables that includefirmware sets.

Service Pack for ProLiantSPP is a comprehensive systems software (drivers and firmware) solution delivered as a singlepackage with major server releases. This solution uses HP SUM as the deployment tool and istested on all supported ProLiant servers including ProLiant Gen9 and later servers.

SPP can be used in an online mode on a Windows or Linux hosted operating system, or in anoffline mode where the server is booted to an operating system included in the ISO file so that theserver can be updated automatically with no user interaction or updated in interactive mode.

For more information or to download SPP, see the Service Pack for ProLiant page at http://www.hpe.com/servers/spp.

SPP release namingSPP versions are named by the year and month that the SPP was released, followed by an identifier.For example,SPP2015.10.0was the first SPP released in October 2015.

Check the SPP release notes for information on the support policy. For more information, see thewebsite at http://www.hpe.com/info/spp/documentation.

Adding or removing components from SPPEach SPP contains a baseline set of components that have been tested together and are supportedfor one year from the release of the SPP, or for five SPP releases, whichever comes first. You cancreate a custom baseline by adding or removing components from the SPP to:

Incorporate a hot fix that was released after the SPP was released.

Ensure that only necessary files are loaded onto the system, which can make tracking changeseasier if troubleshooting is required.

Match the compatibility list with third-party products. For example, if HP releases an updateto your FC HBA, but the vendor of your external switch does not support the HP version, youcan remove this update to continue to receive support from the switch vendor.

Make the baseline smaller so fewer system resources are required.

For more information on creating a custom ISO, seeCreating a custom ISO or baseline (page20).

NOTE: HP SUM 7.x and higher supports creating custom baselines and bootable ISOs. For moreinformation on creating custom baselines and ISOs, see theHP Smart Update Manager User Guideavailable at http://www.hp.com/go/hpsum/documentation.

You can download the latest version of HP SUM from: http://www.hp.com/go/hpsum.

Downloading the SPPProcedure 1

1. In a web browser, go to the SPP website at http://www.hpe.com/servers/spp/download.2. Click the version of the SPP you want to download.3. ClickDownloadnext to the SPP ISO you want to download.

Release sets 19
http://www.hpe.com/servers/spphttp://www.hpe.com/servers/spphttp://www.hpe.com/info/spp/documentationhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsumhttp://www.hpe.com/servers/spp/downloadhttp://www.hpe.com/servers/spp/downloadhttp://www.hp.com/go/hpsumhttp://www.hp.com/go/hpsum/documentationhttp://www.hpe.com/info/spp/documentationhttp://www.hpe.com/servers/spphttp://www.hpe.com/servers/spp


20/34

4. ClickObtain Software. Downloading the software requires an active warranty, HP Care Pack,or support agreement linked to your Support Center profile.

Integrity firmware bundlesThe Integrity website includes updates for servers as specific system downloadable bundles. Formore information on the bundles, see the Integrity website at http://www.hp.com/go/integrity.On the support page for each server, there are two bundles for each firmware release. Use thebundle for the operating system of the management station where you run HP SUM. Both bundles

can update Integrity servers running any operating system because updates are performed throughthe management interfaces. Use one bundle when you run HP SUM on a Windows managementserver to update Integrity servers on the network. Use the other bundle when you run HP SUM ona Linux management server to update Integrity servers on that network. Both bundles contain thesame target server firmware.

You can download the latest version of HP SUM from: http://www.hp.com/go/hpsum.

After you download a bundle, extract the file into empty directory. If you need to update usingmultiple Integrity bundles, download and extract each bundle into its own empty directory. RunHP SUM from the latest bundle you downloaded. In HP SUM, add all bundles to the BaselineLibrary screen. For more information, see theHP Smart Update Manager Online HelporHP SmartUpdate Manager User Guide.

HP SUM provides installation logic and version control that automatically checks for dependencies,and installs only the correct updates for optimal configuration.

Downloading Integrity bundles1. In a web browser, go tohttp://www.hp.com.2. ClickSupport & Drivers.3. ClickDrivers & Software.4. Enter your product name or number, and then pressEnter.5. Select your product from the list.6. ClickCross operating system (BIOS, Firmware, Diagnostic, etc.).7. Choose the firmware, and then clickDownload.

Moonshot Component PackMoonshot Component Pack is a comprehensive firmware solution tested on the Moonshot Systemand delivered as a compressed file. The compressed file includes all the component files neededto update a Moonshot System. Users deploy the firmware updates contained in the MoonshotComponent Pack via the iLO Chassis Manager CLI or Moonshot-45G/180G Switch Module CLI.This can be accomplished using HP SUM, which is included with the files, or manually.

Downloading the Moonshot Component Pack

1. In a web browser, go to the Moonshot website at http://www.hpe.com/servers/moonshot/download.

2. Click the Full Component Pack version.3. Follow the instructions on-screen.

Creating a custom ISO or baselineHP SUM 7.0.0 and later supports creating custom baseline and bootable ISOs. This enables youto minimize the size of the baseline you are deploying, create a standardized baseline for specificenvironments, and minimize the required resources to deploy updates.

The custom baseline or ISO contains only the update components that you select.

20 Firmware and software deliverables
http://www.hp.com/go/integrityhttp://www.hp.com/go/hpsumhttp://www.hp.com/http://www.hpe.com/servers/moonshot/downloadhttp://www.hpe.com/servers/moonshot/downloadhttp://www.hpe.com/servers/moonshot/downloadhttp://www.hpe.com/servers/moonshot/downloadhttp://www.hp.com/http://www.hp.com/go/hpsumhttp://www.hp.com/go/integrity


21/34

Requirements to create a custom baseline:

SPP

Critical or hot-fix updates, if available

An empty directory for each custom baseline or ISO

NOTE: HP SUM does not support creating directories. Do not put more than one baselineISO in a directory.

HP Smart Update Manager

NOTE: SPP includes a version of HP SUM that deploys the included updates. You can alsodownload the latest version of HP SUM at http://www.hp.com/go/hpsum.

If you want to create an ISO, download and unpack an HP SUM or SPP ISO. These ISOsinclude HP SUM-specific data that properly creates the ISO.

NOTE: The HP SUM ISO does not contain any components to update systems. The SPP ISOor Integrity bundles include HP SUM and components you can deploy.

Directory with baselines that contain the updatesTo create a custom ISO:1. Download an HP SUM or SPP ISO.2. Unpack the ISO.3. Launch HP SUM.4. On the Baseline Library screen, click+Add Baseline. Do this for each baseline that include

updates you want to include. HP SUM inventories each baseline you add.5. ClickActionsCreate Custom.6. Enter the following information: Description, version, output location (where HP SUM will save

the baseline or ISO), and select whether you want to create an ISO. If you want to create an

ISO, enter the directory path that includes a valid unpacked SPP or HP SUM ISO. If you runningHP SUM 7.3.0 or later and have more than one version of HP SUM on your system, selectthe version of HP SUM you want to include in the custom ISO or baseline.

7. Select the filters you want to use to select components that might apply to your environment.ClickFilter.

8. HP SUM displays the updates that meet the filters. You can select the components that youwant to include and deselect the components you dont want to deploy.

9. ClickCreate ISO and save Baseline or Save Baseline.

For the full instructions on creating a custom baseline or ISO, see theHP Smart Update ManagerUser Guide, available at http://www.hp.com/go/hpsum/documentation.

Creating a custom ISO or baseline 21
http://www.hp.com/go/hpsumhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum


22/34

6 Update tools

HP SUMHP SUM is included in many update bundles for installing and updating firmware and softwareon ProLiant servers, and firmware on Integrity and Moonshot servers.

HP SUM provides a web-based GUI, interactive command-line, and a command-line scriptable

interface for: Deployment of firmware for single or one-to-many ProLiant and Integrity servers and

network-based targets such as iLO, OA, and VC Ethernet and Fibre Channel modules.

Deployment of software for single or one-to-many ProLiant servers (supported in Windows andLinux environments).

HP SUM has an integrated hardware and software discovery engine that finds the installed hardwareand current versions of firmware and software in use on nodes you identify. HP SUM installs updatesin the correct order and ensures that all dependencies are met before deploying an update. HPSUM prevents an installation if there are version-based dependencies that it cannot resolve.

Key features of HP SUM include:

Dependency checking, which ensures appropriate installation order and component readiness.

Automatic and wizard-like Localhost Guided Update process.

Web browser based application.

Create custom baselines and ISOs.

Download updates from the web.

Intelligent deployment of only required updates.

Simultaneous firmware and software deployment for multiple remote nodes in GUI, interactiveCLI, and CLI modes.

Improved deployment performance. Local online deployment of ProLiant servers and enclosures.

Remote (one-to-many) online deployment of ProLiant and Integrity servers and enclosuresdirectly to each server or using Scalable Update powered by iLO Federation.

Local offline firmware deployments with Service Pack for ProLiant deliverables.

Remote offline deployment when used with Scalable Update powered by iLO Federation, theSmartStart Scripting Toolkit (ProLiant G7 and earlier servers), Scripting Toolkit (ProLiant Gen8and later), iLO Virtual Media, or PXE booted media.

Support for deploying firmware updates to supported Integrity servers and Superdome 2enclosures.

Support for updating VC modules on Integrity servers.

NOTE: HP SUM does not support third-party controllers. This includes flashing hard drivesbehind these controllers.

Remote online deployment of I/O Card firmware on ProLiant and Integrity targets runningHP-UX

For information about HP SUM, seeHP Smart Update Manager User Guide, available on the HPSUM documentation website at http://www.hp.com/go/hpsum/documentation.

22 Update tools
http://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentation


23/34

HP SIM and Version Control AgentHP SIM enables system administrators to manage their systems. It provides hardware levelmanagement for ProLiant, Integrity, and 9000, BladeSystem servers, and StorageWorks MSA,EVA, and XP storage arrays. HP SIM enables you to quickly determine if a server is in alignmentwith a given baseline. With the HP SIM built-in report generation capabilities, you can quicklygenerate reports that show which servers are out of date.

For more information, see the HP SIM website at http://www.hp.com/go/hpsim.

NOTE: An MDS600 firmware update requires that all blades, except the blade performing theupdate, be powered off before you begin the firmware update.

OneViewOptimized for collaboration, productivity, and reliability, the OneView application is designed toprovide simple, unified lifecycle management for the complex aspects of enterprise ITservers,networking, software, power and cooling, and storage.

ArchitectureOneView is delivered as a virtual application running in a VMware vSphere virtual machine.

In contrast to management environments that require predefined serialized workflows and differenttools for different tasks, OneView is a scalable resource-oriented solution focused on the entire lifecyclefrom initial configuration to on-going monitoring and maintenanceof both logical andphysical resources:

Logical resources are items such as networks, server profiles, and connections.

Physical resources are items you can touch, such as server hardware, interconnects, andenclosures.

Software-defined flexibilityyour experts design configurations for efficientand consistent deployment

The application provides several software-defined resources, such as groups and server profiles,to enable you to capture the best practices of your experts across a variety of disciplines, includingnetworking, storage, hardware configuration, and operating system build and configuration. Byhaving your experts define the server profiles and the networking groups and resources, you caneliminate cross-silo disconnects. By using role-based access control (RBAC) and the groups, sets,and server profiles established by your experts, you can enable system administrators to provisionand manage thousands of servers without requiring that your experts be involved with every serverdeployment.

One tool and one data setOneView combines complex and interdependent data center provisioning and management intoone simplified and unified interface. You use one tool and one model to:

Provision the data center.

Manage and maintain firmware and configuration changes.

Monitor the data center and respond to issues.

The solution also provides core enterprise management capabilities, including:

Availability features.

Security features.

Graphical and programmatic interfaces.

Integration with other HP management software.

HP SIM and Version Control Agent 23
http://www.hp.com/go/hpsimhttp://www.hp.com/go/hpsim


24/34

VCSUBladeSystem c-Class VCSU enables administrators to perform the following tasks:

Upgrade VC Ethernet and VC-Fibre Channel module firmware.

Perform other maintenance tasks remotely on VC Ethernet and Fibre Channel modules installedin both the BladeSystem c-Class c7000 and c3000 enclosures using a standalone Windowsor Linux-based CLI.

Sometimes you must use VCSU instead of HP SUM to update a VC module.When VCSU initiates a firmware upgrade process, all modules can be updated at the same time,or the updates can be alternated between left and right modules so that network and SANconnectivity is not disrupted during the upgrades. The utility displays a message indicating that anupdate is in progress and the percentage completed. After the module firmware updates arecomplete, the utility activates all modules. VCSU minimizes outage time in the network fabric andcan eliminate an outage if the VC modules are installed in redundant pairs.

To locate the latest version of VCSU:

1. Open a web browser and go tohttp://www.hp.com.2. ClickSupport and Drivers.3. SelectDownload drivers and software (and firmware).4. Enter BladeSystem c-Class VCSU and pressEnter.5. Select the VC module type.6. Select the operating system for updating the VC module. Always perform a health check of

the VC modules you are going to update before initiating the firmware update process.

NOTE: HP SUM leverages VCSU included in the VC firmware component to deploy VCfirmware updates.

When to use VCSU

Use VCSU if one of the following applies to a VC module:

Unhealthy stateHP SUM reports a module as unhealthy during discovery on the Select Targetsscreen.

Force the same versionHP SUM does not allow you to force rewrite the same firmwareversion.

Downgrade VCMHP SUM does not allow you to force downgrade VC firmware.

Update single moduleHP SUM does not allow you to update only a single module.

Non-redundant configurationIf HP SUM detects that the VC module is non-redundant, it willnot allow you to perform any updates. This prevents an accidental server outage.

Not part of a domainHP SUM alerts you if the VC module is not part of a domain. HP SUMrequires the VC module to be part of a domain to perform discovery.

Change activation orderIf you want to change the activation order, insert time delay for VCmodules, or choose other non-default options.

The VC modules are managed by VCEMIf VC module is managed by VCEM, you need toput the VC module into maintenance mode. After changing to maintenance mode, rescan the

VC module in HP SUM and continue with the update.

Do not use VCSU on enclosures managed by OneView. OneView manages VC firmwareupdates.

24 Update tools
http://www.hp.com/http://www.hp.com/


25/34

SCCMMicrosoft SCCM 2007 enables customers to use SCCM for update management and distributionof ProLiant server system software and PSPs. See the documentation that comes with SCCM forinstructions on how to manage updates with SCCM.

HP has developed an Updates Catalog cabinet file (ProLiant.cab) containing an XML file thatconforms to the Microsoft update format to describe updates available from HP. This cabinet fileenables SCCM to understand and interpret the update status for ProLiant servers. You can monitor

ProLiant server update status and authorize and deploy software updates to servers. Deploymentof PSPs is comprehensive. You receive the benefit of deploying PSPs, which are tested together toensure a smooth installation. Using the SCUP tool, the catalog can be imported into the SCCMserver. The SCCM server can deploy software from the imported catalog to client servers. SCUPworks with the WSUS and SCCM. It is a separate installation by the administrator.

Managing and deploying ProLiant SmartStart components and ProLiant Support Packs only requiresSCCM 2007, WSUS, and SCUP installation. SCCM, WSUS, and SCUP must be installed andverified before managing updates. See the documentation for detailed SCCM, WSUS, and SCUPsetup information on the Microsoft website athttp://www.microsoft.com.

The Server Updates Catalog should be used for monitoring and deploying software and firmwareupgrades, as well as new and upgrade installations of the SPP. Initial installations for individual

software and firmware are not supported due to the complexity of inter-component dependency.Deployment of PSP is recommended for newly-configured ProLiant servers to ensure all relevantsoftware is installed.

SCCM 2007 uses the WSUS infrastructure for delivering software updates to managed devices.Though some of the user experience is similar to SMS 2003, the architecture is different and usesa custom HP-provided scan tool along with standard packages and advertisements. The new SCCMinfrastructure does not support the SMS 2003 Inventory Tool for ProLiant and Integrity Update.

Use SCCM to update SPPs, software updates, and specific firmware updates. If you have SCCM,you need additional tools to complete firmware updates.

NOTE: SCCM cannot be used to update firmware on non-server targets, for example, OA, VC,

and other enclosure interconnects.

VMware ESXi firmware updates

VMware ESXi 5.0 and laterHP SUM 7.1.0 and later supports online firmware and driver updates for VMware ESXi 5.x andlater targets. Run HP SUM on a Windows or Linux host system, and update your VMware targetsover a network. VMware updates are available in the SPP. For more information on releasedcomponents, see theSupport Pack for ProLiant Release Notes. A recommended list of drivers andfirmware for ProLiant servers running VMware ESXi 5.x and later is available in, the VMwareFirmware and Software Recipe at http://vibsdepot.hp.com/.

HP SUM requires the WBEM Providers for VMware ESXi to update the VMware targets. Forinformation on using HP SUM to update VMware targets, see the HP Smart Update Manager UserGuide.

VMware ESXi 4.x and earlierTo update the firmware on a server blade running VMware ESX or ESXi, evacuate the VM gueststo an alternate host before shutting down the VMs. To update the firmware on these servers, usethe SPP. Even though the firmware update process involves offline updates, use the same installationorder that is used for server blades that already have an installed operating system. Therecommended installation order follows.

SCCM 25
http://www.microsoft.com/http://vibsdepot.hp.com/http://vibsdepot.hp.com/http://www.microsoft.com/


26/34

NOTE: A purple screen (PSOD) will be displayed in VMware ESXi 4.1 during either installationof, or upon reboot after, an offline firmware update using the HP Firmware Update DVD 9.0, orlater (containing QLogic NIC Firmware Version 4.0.520 or later) if the server contains an HPNC522m Dual Port 10GbE Multifunction BL-c Adapter, an HP NC522SFP Dual Port 10GbE GigabitServer Adapter, or an NC524SFP Module. For more information on how to resolve this issue, seethe advisory located website at http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982.

26 Update tools
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c02496982


27/34

7 Collecting installed versions of dataCreating a database or spreadsheet of your current server or enclosure configurations before andafter an update will help you to audit your systems, or troubleshoot if you run into problems afteran update.

HP SUM includes functions that enable you to create reports automatically from the command lineor the HP SUM GUI. For more information, see the HP Smart Update Manager User Guideon theHP SUM documentation website at http://www.hp.com/go/hpsum/documentation.

27
http://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentation


28/34

8 Support and other resources

Contacting HPFor worldwide technical support information, see the HP support websitehttp://www.hp.com/go/HPESC.

Be sure to have the following information available before you contact HP:

Active Health System log:

Download and have available an Active Health System log for seven days before the failurewas detected. For more information, see theHP iLO 4 User GuideorHP Intelligent ProvisioningUser Guideon the HP Enterprise Information Library website at http://www.hp.com/go/ilo/docs.

Onboard Administrator SHOW ALL report (for HP BladeSystem products only): For moreinformation on obtaining the Onboard Administrator SHOW ALL report, see the HP websiteathttp://www.hp.com/go/OAlog.

Technical support registration number (if applicable)

Product serial numbers Product model name and number

Product identification number

Applicable error messages

Add-on boards or hardware

Third-party hardware or software

Operating system type and revision level

If you are performing updates in online mode, runGatherLogs, which is included with HPSUM. Run the application from a media device that has read/write permissions.

Related information

WebsiteDocument title

http://www.hp.com/go/ilo/docsHP iLO 4 User Guide



http://www.hp.com/support/IP_RN_enHP Intelligent Provisioning Release Notes

http://www.hp.com/support/SPP_UG_enService Pack for ProLiant Quick Start Guide

http://www.hp.com/support/HP_SUM_UG_enHP Smart Update Manager User Guide

http://www.hp.com/support/HP_SUM_RN_enHP Smart Update Manager Release Notes

http://www.hp.com/go/hpsum/documentationHP SUM Best Practices Implementation Guide

http://www.hp.com/go/hpsum/documentationHP SUM Best Practices Planning Guide

http://www.hp.com/go/oneview/docsHP OneView User Guide

http://www.hp.com/go/vc/manualsHP BladeSystem c-Class Virtual Connect Support UtilityUser Guide

http://www.hp.com/go/vc/manualsHP Virtual Connect Firmware Upgrade Steps andProcedures

http://www.hp.com/go/HPESChttp://www.hp.com/go/HPESChttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/OAloghttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/ilo/docshttp://www.hp.com/support/IP_RN_enhttp://www.hp.com/support/SPP_UG_enhttp://www.hp.com/support/HP_SUM_UG_enhttp://www.hp.com/support/HP_SUM_RN_enhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/oneview/docshttp://www.hp.com/go/vc/manualshttp://www.hp.com/go/vc/manualshttp://www.hp.com/go/vc/manualshttp://www.hp.com/go/vc/manualshttp://www.hp.com/go/oneview/docshttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/go/hpsum/documentationhttp://www.hp.com/support/HP_SUM_RN_enhttp://www.hp.com/support/HP_SUM_UG_enhttp://www.hp.com/support/SPP_UG_enhttp://www.hp.com/support/IP_RN_enhttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/OAloghttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/ilo/docshttp://www.hp.com/go/HPESChttp://www.hp.com/go/HPESC


29/34

WebsiteDocument title

http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA4-7994ENW&cc=us&lc=en

Deploying and updating VMware vSphere 5 on HP ProLiantServers

http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA5-0247ENW&cc=us&lc=en

Best Practices for updating VMware-based HP ProLiantserver firmware and drivers

You can find these documents from the SPP Information Library website at:

Websites

SPP website: http://www.hp.com/go/spp

SPP downloads and available hot fixes: http://www.hp.com/go/spp/download

HP Smart Update Manager: http://www.hp.com/go/hpsum

ProLiant server operating system support matrices: http://www.hp.com/go/supportos

StorageWorks Modular Smart Arrays support matrix website: http://www.hp.com/go/msa

OneView:http://www.hp.com/go/oneview

Virtual Connect: http://www.hp.com/go/vc/manuals

HP and VMware:http://www.hp.com/go/vmware

HP Software Delivery Repository vibsdepot: http://vibsdepot.hp.com/

Microsoft website:http://www.microsoft.com

For information about Linux operating systems, refer to one of the following websites:

Red Hat Linux:http://www.redhat.com

SUSE Linux:http://www.suse.com

Typographic conventionsTable 1 Document conventions

ElementConvention

Cross-reference links and e-mail addressesBlue text:Table 1 (page 29)

Website addressesBlue, underlined text: http://www.hp.com

Boldtext Keys that are pressed

Text typed into a GUI element, such as a box

GUI elements that are clicked or selected, such as menuand list items, buttons, tabs, and check boxes

Text emphasisItalic text

Monospace text File and directory names

System output

Code

Commands, their arguments, and argument values

Monospace, italic text Code variables

Command variables

Emphasized monospace textMonospace, bold text

Typographic conventions 29
http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA4-7994ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA4-7994ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA5-0247ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA5-0247ENW&cc=us&lc=enhttp://www.hp.com/go/spphttp://www.hp.com/go/spp/downloadhttp://www.hp.com/go/hpsumhttp://www.hp.com/go/supportoshttp://www.hp.com/go/msahttp://www.hp.com/go/oneviewhttp://www.hp.com/go/vc/manualshttp://www.hp.com/go/vmwarehttp://vibsdepot.hp.com/http://www.microsoft.com/http://www.redhat.com/http://www.suse.com/http://www.hp.com/http://www.hp.com/http://www.suse.com/http://www.redhat.com/http://www.microsoft.com/http://vibsdepot.hp.com/http://www.hp.com/go/vmwarehttp://www.hp.com/go/vc/manualshttp://www.hp.com/go/oneviewhttp://www.hp.com/go/msahttp://www.hp.com/go/supportoshttp://www.hp.com/go/hpsumhttp://www.hp.com/go/spp/downloadhttp://www.hp.com/go/spphttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA5-0247ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA5-0247ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA4-7994ENW&cc=us&lc=enhttp://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA4-7994ENW&cc=us&lc=en


30/34

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

NOTE: Provides additional information.



31/34

9 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

31
mailto:[email protected]:[email protected]


32/34

Acronyms and abbreviationsBIOS Basic Input/Output System

CD compact disc

CLI Command Line Interface

CNA Converged Network Adaptor

CPLD Complex Programmable Logic DeviceCPU central processing unit

DHCP Dynamic Host Configuration Protocol

DNS domain name system

DVD digital video disc

EVA Enterprise Virtual Array

FDT Firmware Deployment Tool

GUI graphical user interface

HBA host bus adapter

HP SIM HP Systems Insight ManagerHP SUM HP Smart Update Manager

I/O input/output

iLO Integrated Lights-Out

iLO 2 Integrated Lights-Out 2

iLO 3 Integrated Lights-Out 3

IP Internet Protocol

IPv4 Internet Protocol version 4

IPv6 Internet Protocol version 6

ISO International Organization for Standardization

ISP Integrity Support Pack

MSA Modular Smart Array

NFS network file system

NIC network interface controller

OA Onboard Administrator

PSP ProLiant Support Pack

PXE Preboot Execution Environment

PXEBOOT Preboot eXecution Environment Enable/Disable utility

RDU Remote Deployment Utility

ROM read-only memoryRPM Red Hat Package Manager

SAN storage area network

SAS serial attached SCSI

SATA serial ATA

SCCM System Center Configuration Manager

SCUP System Center Updates Publisher

SPP Service Pack for ProLiant

SUM software update manager

SUV serial, USB, video

32 Acronyms and abbreviations


33/34

URL uniform resource locator

USB universal serial bus

VC Virtual Connect

VCM Virtual Connect Manager

VCSU Virtual Connect Support Utility

VM Virtual Machine

WSUS Windows Server Update Services

33


34/34

Index

Bbundles

Integrity,20

CCLI (Command Line Interface),22Collecting data center information,27collection, Updates,19Command Line Interface (CLI),22configuration, SCCM,25contacting HP,28conventions

document, 29text symbols,30

Ddeliverables

firmware and software deliverables,19Integrity Support Pack,20

deploying firmware,22deployment methods,19deployment scenarios

CloudSystem Matrix,11Distributed corporate customer,8Large data center,9Updating a single enclosure,7

deployment software,22deployment to multiple remote hosts

Distributed corporate customer,8

Large data center,9deployment toolsUpdate tools,22

documentconventions,29related documentation,28

documentationExplanation of guides,5HP website,29providing feedback on,31

driver and software information,27

Ffirmware

firmware and software deliverables,19firmware management

Services overview,12

Ggraphical user interface (GUI),22GUI (graphical user interface),22

H

HP Smart Update Manager overview,23

IIntegrity bundles,20Integrity servers,20

introduction, 5MMicrosoft software,25modifying the SPP ISO,20

Ooverview,5overview, guide,5

Rrelated documentation,28reports, creating,27

Sscenarios, deployment

Server environment scenarios,6scenarios, overview

CloudSystem Matrix,11Distributed corporate customer,8Large data center,9Server environment scenarios,6Updating a single enclosure,7

scripted deployment,22support, Systems Insight Manager,23

symbols in text,30Systems Insight Manager,23

Ttechnical support,28text symbols,30typographic conventions,29

VVersion Control Agent (VCA),23Virtual Connect modules,24

Wwebsites

product manuals,29

Documents

HP Server Best Practices Guide