HP Smart Update Manager Release Notes HP Part Number: 679985-002 Published: June 2012 Edition: 2
© Copyright 2012 Hewlett-Packard Development Company, L.P. Open source software • OpenPegasus version 2.10.0 For more information, see the OpenPegasus website at http://www.OpenPegasus.org. • Mongoose version 2.11 For more information, see the Mongoose website at http://sourceforge.net/projects/mongoose/develop. • open-WSMan For more information, see the open-WSMan website at http://sourceforge.net/projects/openwsman/.
Version 5.1.0 Description HP SUM is a technology included in many HP products, including the Service Pack for ProLiant (SPP), for installing and updating firmware and software components on HP ProLiant and HP Integrity servers, BladeSystem enclosures, and options. HP SUM provides a GUI and a command-line scriptable interface for: • Deployment of firmware for single or one-to-many HP servers and network-based targets such as iLOs, OAs, and VC Ethernet and Fibre Channel modules.
Fixes The following known issues have been resolved in this version of HP SUM: • The Install Options and Feedback screens have not been localized in Japanese. • HP SUM for Windows version 5.0.0 in Japanese will show corrupted names for NICs in the generated firmware report. • Report Generation with CLI is not correct. • The top three buttons are not available if a target with no applicable components is selected. • HP SUM might show the installed version of P2000/MSA2000 components as NULL.
NOTE: HP Smart Update Manager requires the user to be logged in using Administrator credentials. A user account elevated to “Run as administrator” in most cases does not have sufficient rights because access to protected system files and the Windows registry is restricted. This access is needed to deploy most firmware and driver updates.
NOTE: When attempting to use the remote deployment functionality of HP SUM on any edition of Windows Server 2008, Windows Vista, or Windows 7, you must ensure that the File and Print Services feature is enabled and that the File and Print Services exception has been enabled in the Windows firewall. Failure to do so prevents HP SUM from deploying to remote Windows targets. • Enable the network ports that HP SUM uses.
Enable the network ports that HP SUM uses. For more information, see the Enabling ports section in the HP Smart Update Manager User Guide. Minimum requirements for Red Hat Enterprise Linux 6 servers • Ensure that each NIC has an IP address assigned. To get the IP address assigned to a NIC, enter the dhclient command in the console, which launches the NIC interfaces and retrieves an IP address. If a NIC does not have an IP address, HP SUM appears to hang on start up.
◦ fontconfig-2.8.0-3.el6.i686.rpm ◦ expat-2.0.1-9.1.el6.i686.rpm ◦ zlib-1.2.3-25.el6.i686.rpm ◦ libstdc++-4.4.4-13.el6.i686.rpm • For Linux deployments, a root equivalent user account must be used. • SSH support must be enabled and the firewall opened to allow SSH communications on remote Linux servers or HP SUM cannot deploy updates. By default, SUSE LINUX Enterprise Server 10 and 11 block SSH support through the firewall.
and Ready for Installation as the status, if the iLO Channel Interface Driver is not installed. This will happen for iLO 2, iLO 3, and iLO4. The firmware might fail to update if it is already current. Suggested action: To view the installed version of the iLO firmware via HP SUM, install the iLO Channel Interface Driver. General Issues You can use HP SUM to deploy Virtual Connect (VC) firmware unless one of the following conditions apply: 1. 2. 3.
HP SUM for Windows and Linux RPM configuration screen has not been localized into Japanese The RPM configuration screen has not been localized into Japanese. Suggested action: There is nothing you need to do, this is expected behavior.
Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
