HP Smart Update Manager Release Notes

Transcription

1 HP Smart Update Manager Release Notes HP Part Number: Published: November 2012 Edition: 4

2 Copyright 2012 Hewlett-Packard Development Company, L.P. Open source software OpenPegasus version For more information, see the OpenPegasus website at Mongoose version 2.11 For more information, see the Mongoose website at open-wsman For more information, see the open-wsman website at zlib version For more information, see the zlib website at libcurl version For more information, see the libcurl website at gsoap version For more information, see the gsoap website at libssh2 version For more information, see the libssh2 website at libxml2 version For more information, see the libxml2 website at libxslt version For more information, see the libxslt website at OpenSSL version 1.0.0d For more information, see the OpenSSL website at

3 Version HP SUM overview HP SUM is a technology you can use to update firmware and software on HP ProLiant servers, and firmware on HP Integrity servers. The HP Service Pack for ProLiant (SPP) and HP Integrity Smart Update Firmware bundles include the version of HP SUM that HP recommends using for the set of updates. HP SUM updates servers, enclosures, and other components in your server environment. 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 ilo, OA, and VC Ethernet and Fibre Channel modules. Deployment of drivers, agents, and tools for single or one-to-many HP ProLiant servers (supported in Windows and Linux environments). NOTE: Ensure that any firewalls between this system running HP SUM and the target servers are opened for the necessary management ports, such as SSH and HTTP. For more information on the ports HP SUM uses and changing firewall settings, see the HP Smart Update Manager User Guide or HP Smart Update Manager Online Help. Operating systems and devices HP ProLiant servers This version of HP SUM is delivered with Red Hat Enterprise Linux 6.3 Supplement for HP Service Pack for ProLiant (B) and HP Service Pack for ProLiant For more information about this product, see the HP Service Pack for ProLiant Information Library at documentation. HP Integrity servers HP SUM can deploy firmware to the following servers: HP Integrity Superdome 2 HP Integrity BL860c i2 HP Integrity BL860c i4 HP Integrity BL870c i2 HP Integrity BL870c i4 HP Integrity BL890c i2 HP Integrity BL890c i4 HP Integrity rx2800 i2 HP Integrity rx2800 i4 HP SUM must be running on a supported Windows or Linux system as noted in the HP Integrity Smart Update Firmware bundle's Release Notes. HP SUM can update the supported target HP Integrity servers that are running any OS or none at all at the time of the update. For more information on HP Integrity Smart Update Firmware bundles, see the Manage HP Integrity Servers Firmware Updates website at HP SUM overview 3

4 Enhancements Fixes Prerequisites Support for updating VMware servers New Installed Updates report The following known issues have been resolved in this version of HP SUM: HP SUM might show HP High Performance ilo 2 Mouse X Driver for Linux as a valid component for an operating system that does not support the mouse driver HP SUM might show the status of HP ProLiant Dynamic Smart Array RAID controller driver for Windows 2008 x64 as Not Updated Already Current after performing an installation. IMPORTANT: Before deploying any components to a system, be sure that a recent backup of the system is available in the event the deployment procedure fails. Enable the network ports that HP SUM uses. For more information, see Network ports used by HP SUM (page 8). Minimum requirements for Windows To successfully use HP SUM to deploy firmware and software to targets running a Windows operating system, the following must be available: A supported operating system: Microsoft Windows Server 2012 Microsoft Windows Small Business Server 2012 Microsoft Windows Small Business Server 2011 & 2011 Essentials Windows MultiPoint Server 2011 (uses Windows Server 2008 R2 drivers) Microsoft Windows Server 2008 R2 Standard, Enterprise, Datacenter, Hyper-V, HPC and Web x64 Editions (Datacenter Edition is for 2 socket servers and above. Full OS and Server Core OS installations required including Hyper-V standalone.) HyperV is supported remotely only. Microsoft Windows Server 2008 Foundation & Foundation R2 - supported on single-socket servers Microsoft Windows Server 2008 Standard, Enterprise, Datacenter, Hyper-V, HPC and Web x86 and x64 Editions (Datacenter Edition is for 2 socket servers and above. Full OS and Server Core OS installations required including Hyper-V standalone.) Microsoft Windows Server 2003 A local administrative system with at least 1 GB of memory NOTE: The HP SPP or HP Integrity Smart Update firmware bundle that delivered HP SUM might require more memory than HP SUM. Check the release notes for those products for information on the memory requirements. Sufficient hard-drive space of at least twice the file size of the components to be deployed WMI enabled on all targets 4 Enhancements

5 All remote targets must be visible on the network by the administrative system running HP SUM An account with administrator privileges on each target server HP recommends that the user name and password for the administrator account on each target server be the same as those on the local administrative system. If administrator privileges are not set up in this manner, you must have the user name and password available for each remote server accessible. Alternatively, you can use a domain account on the local administrative system that has administrator privileges on the target servers. HP SUM 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, which is needed to deploy most firmware and driver updates, is restricted. If the logged in account is unable to perform the net use * \\server\admin$ for Microsoft Windows targets, you do not have sufficient privileges to run HP SUM to remote targets. The beginning and ending IP addresses entered for the range of targets must both be on the same subnet. 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. For more information, see Network ports used by HP SUM (page 8). Minimum requirements for Linux servers To successfully use HP SUM to perform dependency checks on targets running a Linux operating system, the following must be available: Supported operating systems: Red Hat Red Hat Enterprise Linux 5 for x86 Red Hat Enterprise Linux 5 for AMD64 and Intel EM64T Red Hat Enterprise Linux 6 for x86 Red Hat Enterprise Linux 6 for AMD64 and Intel EM64T Novell SUSE LINUX Enterprise Server 11 for x86 SUSE LINUX Enterprise Server 11 for AMD64 and Intel EM64T SUSE LINUX Enterprise Server 10 for x86 SUSE LINUX Enterprise Server 10 for AMD64 and Intel EM64T A local administrative system with at least 1 GB of memory NOTE: The HP SPP or HP Integrity Smart Update firmware bundle that delivered HP SUM might require more memory than HP SUM. Check the release notes for those products for information on the memory requirements. glibc or later Prerequisites 5

6 gawk or later sed or later pciutils i386.rpm or later Be sure that the following platform-specific compatibility libraries are also installed. For Red Hat Enterprise Linux 5 x86 servers: libnl (required for QLogic and Emulex drivers and firmware) For Red Hat Enterprise Linux 5 AMD64/EM64T servers: libnl (required for QLogic and Emulex drivers and firmware) For SUSE Linux Enterprise Server 10 x86 servers: libnl (required for QLogic and Emulex drivers and firmware) For SUSE LINUX Enterprise Server 10 AMD64/EM64T servers: libnl (required for QLogic and Emulex drivers and firmware) e2fsprogs-32bit NOTE: This library is graphical only, however, it is required to use HP SUM in Console mode. fontconfig-32bit For SUSE LINUX Enterprise Server 11 x86 servers: libstdc i586 or later libnl (required for QLogic and Emulex drivers and firmware) For SUSE LINUX Enterprise Server 11 AMD64/EM64T servers: libstdc bit or later libnl (required for QLogic and Emulex drivers and firmware) Enable the network ports that HP SUM uses. For more information, see Network ports used by HP SUM (page 8). 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. Red Hat Enterprise Linux 6 console mode 6 Prerequisites

7 NOTE: No X console in either x86 or x86_64 servers. To run HP SUM in silent mode, you must install the base server with defaults and the following RPMs. Load the hp-snmp-agents rpm and rpms based on hp snmp agent: lm_sensors-libs el6.<arch>.rpm net-snmp-libs el6.<arch>.rpm net-snmp el6.<arch>.rpm To build Linux drivers from source: kernel-headers el6.<arch>.rpm redhat-rpm-config el6.noarch.rpm kernel-devel el6.<arch>.rpm rpm-build el6.<arch>.rpm gcc el6.<arch>.rpm Red Hat Enterprise Linux 6 graphical mode NOTE: The following RPMs must be the 32-bit version even under x86_64 architecture as Linux distributions, HP SUM, and several of the RPMs require 32-bit libraries installed. Red Hat Enterprise Linux 6 console mode RMPs libuuid el6.i686.rpm freetype el6.i686.rpm libsm el6.i686.rpm libice el6.i686.rpm libxi el6.i686.rpm libx el6.i686.rpm libxext el6.i686.rpm libxcb el6.i686.rpm libxau el6.i686.rpm libxrender el6.i686.rpm libxrandr el6.i686.rpm libxfixes el6.i686.rpm libxcursor el6.i686.rpm fontconfig el6.i686.rpm expat el6.i686.rpm zlib el6.i686.rpm libstdc el6.i686.rpm Prerequisites 7

8 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. To enable SSH support if it has been disabled in the firewall, use the yast2 command to open the necessary ports in the Linux firewall. IMPORTANT: HP SUM has limited cross-platform deployment support. Deployments from Windows to Linux are supported, but deployments from Linux to Windows are not supported. Network ports used by HP SUM HP SUM requires that certain network ports are available for proper operation. If you lock down network ports, remember to ensure that the ports listed in the network port tables are open so that HP SUM works correctly when connecting to remote target servers and hosts. If you are unable to unlock these network ports, the only option is to run HP SUM locally and update network-based hosts, such as the OA, ilo, and VC modules, through their web interfaces. The SOAP server that HP SUM launches uses ports 443 or You can define your own ports by modifying the hpsum.ini file. 1. Open hpsum.ini in a text editor. You can find the file in the same folder as the HP SUM application. 2. Look for the following lines: Port=443 AlternatePort= Change the AlternatePort to a port free of another web service. NOTE: For security reasons, HP does not recommend changing the main port from port 443. Table 1 HP SUM Windows network ports Ports Port 443 Ports 445 and 137/138/139 (Port 137 is used only if you are using NetBIOS naming service.) Port Ports 80 or Ports 21 or Description A secure data port used to transfer information. Connects to the remote ADMIN$ share on target servers. These are the standard ports Windows servers use to connect to the remote file shares. If you can connect remotely to a remote Windows file share on the target server, then you have the right ports open. Default for some internal communications. This port listens on the remote side if there is no conflict. If a conflict occurs, the next available port is used. Logs are passed to the target and retrieved through an internal secure web server that uses port 80 if it is available. If it is not available, the Web server uses first available port in the range of This support allows updates of the ilo and VC firmware without the need to access the host server. It also allows the servers to run VMware or other virtualization platforms to update the ilo firmware without requiring a server reboot or a migration of the virtual machines to other servers. NOTE: HP SUM attempts to determine if a server running HP SUM also hosts a web server. In some cases, HP SUM cannot detect an existing web server and attempts to use port 80. If this occurs, installations that are using HP SUM will fail. If failure occurs, you can move HP SUM to another server or workstation that is not already running a web server. You can also disable the web server until HP SUM installations are complete. You can use these FTP ports to perform switch updates. 8 Prerequisites

9 Table 2 HP SUM Linux network ports Ports Port 22 Port 443 Port Ports 80 or Ports 21 or Description Establishes a connection to the remote Linux server via SSH. For Integrity servers, HP SUM uses this port to discover target settings. A secure data port used to transfer information. Default for some internal communications. It listens on the remote side if there is no conflict. If a conflict occurs, the next available port is used. Updates are passed to the target and retrieved through an internal secure web server that uses port 80 if it is available. If it is not available, the Web server uses first available port in the range of This support allows ilo and VC firmware updates without having to access the host server. It also allows servers running VMware or other virtualization platforms to update their ilo without having to reboot their server or to migrate their virtual machines to other servers. NOTE: HP SUM attempts to determine if a server running HP SUM also hosts a web server. In some cases, HP SUM cannot detect an existing web server and attempts to use port 80. If this occurs, installations that use HP SUM will fail. If failure occurs, move HP SUM to another server or workstation that is not already running a web server. You can also disable the web server until HP SUM installations are complete. You can use these FTP ports to perform switch updates. Installation instructions Installing HP SUM from the SPP or HP Integrity Firmware bundles: 1. Download the HP SPP or HP Integrity Smart Update Firmware bundle. 2. Extract the HP SPP or HP Integrity Smart Update Firmware bundle. 3. Do one of the following: Run HP SUM in online mode Double-click the hpsum.exe (Windows) or hpsum (Linux). Run HP SUM in offline mode (HP ProLiant servers only) Place a DVD or bootable USB key with the HP SPP into the target you want to update. For more information on how to install the HP SPP or HP Integrity Smart Update Firmware bundle, see the release notes for those products. Issues and suggested actions General issues The following are known issues and limitations with HP SUM. HP SUM is unable to configure components on Windows Hyper-V HP SUM will not run on Windows Hyper-V. Components must be configured from a different system and can be deployed remotely to the Hyper-V server. Hyper-V is only supported as a target server, not a deployment server. Suggestion action: No action. This is expected behavior. If you deselect a target during the discovery process, HP SUM will continue to discover the target On the Select Target screen, if you deselect a target while HP SUM is attempting to discover it, HP SUM will continue the discovery process. You cannot proceed until HP SUM finishes the discovery process. Suggestion action: No action. This is expected behavior. Installation instructions 9

10 HP SUM does not report FC HBA and CNA firmware versions HP SUM does not report FC HBA and CNA firmware versions. When running either the HPSUM_UpdateTobeApplied_Report or the firmware report, neither will report the drivers/firmware that needs to be updated. Suggestion action: No action. This is a known limitation. On HP SUM for Windows, ilo installed firmware version will show as None, if the Channel Interface Driver is not installed When updating a system using the HP Service Pack for ProLiant, on the Select Bundle or Select Component page, the ilo firmware will show None as the installed version and Ready for Installation as the status, if the ilo Channel Interface Driver is not installed. 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. You cannot use HP SUM to deploy Virtual Connect (VC) firmware if one of the following conditions applies 1. If the VC is in one of the following states: Unhealthy VC module Non-redundant VC configuration Not all VC modules are part of a domain 2. If you want to: Manually choose the order of component deployment Back-up the configuration before flashing the VC firmware 3. Downgrade the VC firmware. Suggested action: Use HP Virtual Connect Support Utility (VCSU) to perform the update or downgrade. NOTE: If the VCs are managed by HP Virtual Connect Enterprise Manager (VCEM), they must first be put into maintenance mode before HP SUM can perform the VC firmware updates. After they are in maintenance or firmware mode, HP SUM and higher, and SPP and later, can be used to update them. After the update, put the VCs back into normal production mode. Virtual Connect (VC) update stops after discovery and installation never begins if the Onboard Administrator (OA) credentials are different from the VC credentials VC update stops after discovery and installation fails to initiate if the OA credentials are different from the VC credentials. Suggested action: Use HP SUM in GUI mode. This issue only occurs when using the command line and Input File modes for HP SUM. When using the Japanese version of HP SUM for windows, if you enter incorrect CLI parameters, HP SUM returns a corrupted string If you enter the incorrect parameters, a HP SUM returns a corrupted string instead of displaying an error message. Suggested action: Verify that the parameters are correct. 10 Issues and suggested actions

11 HP SUM for Windows and Linux does not have Japanese translations for some text The following screens do not have Japanese localized text: RPM configuration page Error messages on the Select Target page Suggested action: No action. This is expected behavior. During a silent installation, HP SUM does not update components that are already up to date When using RDP and the command /hpsum/express_install/silent, components that are current are not updated. Suggested action: No action is required. The components are already current. HP SUM on a Linux system cannot find Smart Components if they are in a directory path that contains spaces If a directory with spaces in the name is created, and a bundle is extracted to that directory, HP SUM cannot find any components when the directory is added a repository. Suggested action: Rename and remove the spaces in the directory path name. This issue does not occur if the bundle is extracted to a different directory without spaces and then copied to a directory with spaces. HP SUM does not run in command line mode without the X libraries HP SUM needs the graphics or X libraries to run from the command line. Suggested action: Install the X libraries to run HP SUM from the command line. HP SUM reports port 80 might be blocked and the target is unable to retrieve files from the HP SUM host If HP SUM cannot connect to a network target, the Installation Log will display the following: ERROR: Target was unable to retrieve firmware files from HPSUM host via HTTP. This could be due to port 80 being blocked by a firewall on HPSUM host. HP SUM tries to use ports 80 and The error only reports port 80. Suggested action: Make sure the firewall is not blocking the ports HP SUM is using. HP SUM displays the message HP SUM has stopped working after you re-analyze and install If you attempt to rewrite software or firmware, HP SUM displays the message HP SUM has stopped working. Suggested action: Exit HP SUM and restart it. HP SUM displays a password error when you try to log into an ilo After you reboot an ilo, HP SUM tries to apply user credentials to the target and displays a message that the user credentials are incorrect. Suggested action: Exit HP SUM and then restart it. HP SUM does not time out when the SSH connection quits responding When HP SUM tries to determine the status of the SSH connection, it does not time out after there is no response. Suggested action: Exit HP SUM and then restart it. Issues and suggested actions 11

12 HP SUM does not report a connection loss with a target during a file transfer If HP SUM loses connection with a target during a file transfer, HP SUM does not report the loss of connectivity. Suggested action: Exit HP SUM and then restart it. HP SUM does not detect HP 60/70 Modular Smart Array in offline mode HP SUM does not detect Modular Smart Array 70 in offline mode. Suggested action: Update the target using the HP 60/70 Modular Smart Array Smart Component. HP ProLiant issues HP SUM for Linux might not list the HP Ethernet 10Gb 2-port 530FLR-SFP+/ 530FLB/530M NIC firmware until the driver is installed and the Ethernet ports are enabled HP SUM will not discover Broadcom NIC firmware physically attached to the server unless the drivers are installed and all the NICs Ethernet ports are open. Suggested action: To update the firmware for Broadcom NICs in Linux, use the following steps: 1. Install the bnx2x driver found in the SPP package, the SDR, or the Linux distribution. 2. Enable all the Ethernet ports. 3. Run the Broadcom firmware upgrade component. HP SUM displays Installation not needed for HP ProLiant Smart Array SAS/SATA Controller Driver version for Windows Server 2008 When using HP SUM version to install software, the HP ProLiant Smart Array SAS/SATA Controller Driver version for Windows Server 2008 is listed as Installation not needed. This driver is required to upgrade the media driver, which is the in-box driver that ships with the operating system, to use the full Smart Array functionality. Suggested action: Ensure that there are no inactive driver files for a device present in c:\windows\ system32\drivers folder after a new operating system installation. As a workaround, run the driver component (hpciss2) independent of HP SUM. HP SUM might pull inapplicable components from the web for certain ProLiant platforms after an installation After installing and rebooting the server, if you use HP SUM to download the latest components from the HP FTP site, HP SUM might pull some inapplicable components. If HP SUM installs the inapplicable components, HP SUM displays the error Update returned an error. Suggested action: On the Select Components screen, do not choose the updates that do not apply to your environment. The installation will proceed normally. HP SUM might show a status for HP ProLiant Dynamic Smart Array RAID controller driver for Windows 2008 x64 as Not Updated Already Current after performing an installation. HP SUM does not install HP ProLiant Dynamic Smart Array RAID controller driver for Windows 2008 x64. Suggested action: If HP SUM displays this error, try to install the component as a stand-alone component. HP SUM for Linux might take longer than 30 minutes to build RPMs on SUSE Linux Enterprise Server 10 Due to the amount of source RPMs that need to build and the build time of each, the build process might take longer than 30 minutes. 12 Issues and suggested actions

13 Suggested action: For more information about resolving this issue, see the Customer Advisory c on the HP support website at Document.jsp?objectID=c Lsi-mpt2sas and Mellanox components might not show up on the Select Bundle page HP SUM might not list the components mellanox-mlnx-en-kmp-bigsmp and lsi-mp2sa-kmp-bigsmp on the Select Bundle page. Suggest action: As a workaround, install the RPMs as stand-alone components. HP SUM might not install Intel Thermal Agents for HP361T NICs HP SUM might not install the thermal agent included in the HP Intel E1R Driver. An issue with dependencies on the CHIF driver causes this issue. Suggest action: You can install the Intel driver as a stand-alone component after the initial HP SUM installation. When using HP SUM on a Linux host, ilo components are not included when using the Check for Latest Updates from ftp.hp.com repository If you are running HP SUM on a Linux host, and using the Check for Latest Updates from ftp.hp.com repository, ilo components might not be downloaded for ProLiant targets because the components are not shown as applicable updates. Suggest action: Use HP SUM on a Windows host to update HP ProLiant and HP Integrity targets. If you need to use a Linux host, use the SPP as a repository to update HP ProLiant servers servers. HP SUM does not generate reports on HP ProLiant BL620c G7 servers running Windows Server 2003 after installing Microsoft hotfix KB There is an issue with HP SUM accessing the WMI namespaces after installing Microsoft hotfix KB Suggested action: Run the following script to resolve the issue: 1. Open Command Prompt. 2. Type cd %windir%\system32\wbem. 3. Execute the following script: HP Integrity issues FOR /f %s in ('dir /b /s *.dll') do regsvr32 /s %s Net stop /y winmgmt FOR /f %s in ('dir /b *.mof *.mfl') do mofcomp %s Net start winmgmt HP SUM does not generate the Failed Dependency report from the command line or input files for Superdome 2 servers HP SUM analyzes Superdome 2 servers after it generates the Failed Dependencies report. HP SUM details the failed dependencies in the HP SUM user log. Suggested action: View the HP SUM user log, or use HP SUM GUI mode to generate the Failed Dependencies report. 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 Documentation feedback 13

14 Include the document title and part number, version number, or the URL when submitting your feedback. 14 Documentation feedback