HP Smart Update Manager (SUM) manual Deploying PSPs, PSP deployment scenarios

Page 8

2 Deploying PSPs

PSPs are deployed using HP SUM. In the PSP for Linux, HP SUM enables support for native RPM files. Users can now deploy firmware and software components simultaneously. PSPs can be deployed using graphical or command-line utilities specific to each operating system.

For more information about PSP deployment with HP SUM, see the HP Smart Update Manager User Guide at http://www.hp.com/support/HP_Smart_Update_Manager_UG_en.

PSP deployment scenarios

Operating system environment

Scenario

Microsoft Windows

Graphical deployment on a single-host system using HP SUM

Graphical deployment remotely on a multiple-host system using the HP SUM GUI

Command-line deployment on a single-host system using the HP SUM CLI

Command-line deployment on a multiple-host system using the HP SUM CLI

Command-line deployment on a multiple-host system managed by HP SIM

Linux

Graphical deployment on a single-host system using HP SUM

 

Graphical deployment remotely on a multiple-host system using the HP SUM GUI

 

Command-line deployment on a single-host system using the HP SUM CLI

 

Command-line deployment on a multiple-host system using the HP SUM CLI

NOTE: If you install a PSP and then install an operating system Service Pack, a Support Pack, or other operating system updates, HP recommends reinstalling the PSP.

Deployment for Microsoft Windows

This section discusses deploying PSPs on Windows operating systems. The PSPs support 32-bit and x86-64-based installations on both AMD- and Intel-based servers.

For a current list of supported operating systems, see the HP PSP website at http://www.hp.com/ servers/psp.

Minimum requirements for Microsoft Windows PSP

IMPORTANT: Before deploying software updates on a host server, be sure that a recent backup of the host server is available in case the deployment procedure fails.

For successful component deployments on Microsoft Windows hosts, the following minimum requirements must be met:

A local administrative system with 512 MB of memory and running a supported Windows operating system must be used.

One or more remote host servers that run a supported Windows operating system and need a software upgrade must be available. If the local administrative system (local host) is the only server that requires an upgrade, then remote host servers are not necessary.

Sufficient hard-drive space, which is generally at least twice the file size of the components you want to deploy, must be available.

WMI must be enabled.

8Deploying PSPs

Image 8
Contents HP ProLiant Support Pack User Guide Page Contents Documentation feedback Acronyms and abbreviations Index Introduction PSP overviewComponents in the PSP Not be available in some casesComponent Description/Benefit Storage-Linux Which does not ship in Red Hat or SuseNew features New featuresObtaining PSP Version control Creating a centralized, network-based software repositoryDeploying PSPs PSP deployment scenariosDeployment for Microsoft Windows Minimum requirements for Microsoft Windows PSPInstalling the PSP for Windows Installing the PSP for WindowsUpgrading a PSP from HP SUM Deploying PSPs for LinuxServer virtualization detection and support Minimum requirements for Linux PSP Minimum requirements for Linux PSPMinimum requirements for Red Hat Enterprise Linux 6 servers Rpm-build-4.8.0-12.el6.arch.rpm Gcc-4.4.4-13.el6.arch.rpm E2fsprogs-32bit Installing or upgrading a PSP for Linux Verifying Installed Components Command-line interface Command-line syntaxCommand-line interface Advanced topicsNo switches UseamsUsesnmp UsewmiCommand-line arguments Installation options Useweb 22.33.4480Installation options Overriding errors Reboot optionsReboot Rebootmessage reboot message Use this argument to select a partition to updateRebootdelay timeoutinsecs RebootalwaysDryrun CurrentcredentialPassword Logdir pathSYSTEMDRIVE%\CPQSYSTEM\hp\ Path\hp\log\netAddressComponent configuration for Windows components only Command-line examples HP SUMReturn codes Linux smart-component return codesInput files Linux RPM return codesError reporting Input file format and rulesFile encoding Input filesInput file parameters Ignoreerrors SourcepathUselatest YES, noWebupdateneeded SoftwareonlyUsecurrentcredential UseproxyserverCmalocalhostrwcommstr CmalocalhostrocommstrCmamgmtstationrwipordns CmamgmtstationrwcommstrHpvcavcrmloginid HpvcavcrmloginpasswdADMIN-GROUP ANONYMOUS-ACCESS10.1.1.1-10.1.1.10 10.2.2.2-10.2.2.10 IP-RESTRICTED-EXCLUDE orIP-RESTRICTED-INCLUDE Trustmode CertlistXenamelist HPQLA2X00FOUpdatetype RebootlistIgnorewarnings DevicelistEND Targets Reports Usage hpsum /reportHpsumReportdate.html HpsumReportdate.xml HpsumInventoryReportdate.html HpsumInventoryReportdate.xmlHPSUMInstalledReportdatatime.xml or Html Report typeInstallation troubleshooting for Microsoft Windows TroubleshootingInstallation troubleshooting for Microsoft Windows Ports Description TroubleshootingPorts Ports 445 and 137/138/139 Installation troubleshooting for Linux How many target devices are selected for installation Send data to the target serverPorts PortHow to contact HP Subscription service Related informationSupport and other resources Information to collect before contacting HPTypographic conventions HP Insight Remote Support softwareWebsites Monospace textHP Insight Remote Support software Documentation feedback Documentation feedbackAcronyms and abbreviations Transmission Control Protocol/Internet ProtocolIndex IndexObtaining PSPs overview