HP Smart Update Manager 4.2 User Guide
Table Of Contents
- HP Smart Update Manager User Guide
- Abstract
- Notice
- Contents
- Introduction
- HP Smart Update Manager overview
- Using this guide
- New features of HP SUM 4.2.0
- Minimum requirements
- Supported deliverables overview
- Deployment from HP SUM
- Executing HP SUM
- Deploying software using the ProLiant Support Pack (PSP) for Microsoft Windows
- Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows
- Deploying software using the ProLiant Support Pack for Linux
- Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD
- Deploying firmware using the HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundles
- HP SUM User Interface
- Deployment scenarios
- Keyboard support
- Local host installations
- Multiple-host installations
- Selecting remote hosts or groups
- Searching for remote hosts
- Managing hosts
- Managing groups
- Entering credentials for hosts
- Selecting bundles to filter on multiple hosts
- Selecting components to install on multiple hosts
- Updating Firmware on HP Integrity BL860c/BL870c/BL890c i2 Servers
- Viewing the installation results for multiple hosts
- Scripted deployment
- Advanced topics
- Troubleshooting
- Recovering from a failed ROM upgrade
- Recovering from an installation failure
- Recovering from a discovery failure
- Recovering from a loss of Linux remote functionality
- Recovering from a blocked program on Microsoft Windows
- Recovering from operating system limitations when using a Japanese character set
- Recovering from Fatal Error - application will exit message
- Recovering from a missing reboot message when running on SUSE LINUX Enterprise Server 9
- Recovering a lost HP Smart Update Manager connection
- Troubleshooting HP Smart Update Manager in IPv6 networks
- HP SUM found new hardware message
- Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source
- Linux component version discrepancy for source RPMs
- HP SUM displays No components found in the selected repository(ies) message
- Additional/Optional Actions columns are grayed when HP SUM is maximized
- Installation of components failed with 'Update returned an error' when installing Linux RPMs
- Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens
- HP SUM fails on Windows Vista® due to McAfee firewalls
- Technical support
- Acronyms and abbreviations
- Index

Troubleshooting 98
Troubleshooting
Recovering from a failed ROM upgrade
Recovering from a failed system ROM upgrade
Use redundant ROM or ROMPaq to recover from a system ROM upgrade failure.
Redundant ROM recovery
When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a
backup, enabling you to switch easily to the alternate ROM version if the new ROM becomes corrupted for
any reason. This feature protects the existing ROM version, even if you experience a power failure while
flashing the ROM.
When the server boots, the server detects if the current ROM is corrupt. If a corrupt ROM is detected, then the
system boots from the backup ROM and sends an alert through POST that the ROM is corrupt.
To access the redundant ROM through RBSU:
1. Power up your desktop. A prompt appears in the upper right corner of the screen.
2. Access RBSU by pressing F9.
3. Select Advanced Options.
4. Select ROM Selection.
5. Select Switch to Backup ROM.
6. Press the Enter key.
7. To exit the current menu, press the Esc key, or to exit RBSU, press the F10 key. The server restarts.
If RBSU is inaccessible, then you can switch ROM images by changing the switch settings on the system
configuration switch. For more information, see your server documentation.
If both ROM images are corrupt, use ROMPaq recovery.
ROMPaq recovery
The Disaster Recovery feature supports systems that do not support the Redundant ROM feature. Disaster
Recovery only applies to platforms with nonredundant system ROM. If both the up-to-date and backup
versions of the ROM are corrupt, then perform ROMPaq Disaster Recovery procedures:
1. On another server, download and save the ROMPaq image to the hard drive from the HP website
(http://www.hp.com).
2. Execute the ROMPaq image to create the ROMPaq disk.
3. Switch to the server with the corrupted ROM.
4. Power down the server.
5. Insert the ROMPaq disk.