HP Smart Update Manager Release Notes Version 6.4.
© Copyright 2012, 2014 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. • zlib version 1.2.
Version 6.4.1 Description HP SUM is a product included in many HP products for installing and updating firmware and software on HP ProLiant servers, and firmware on HP Integrity servers. HP SUM provides a web-based GUI and a command-line scriptable interface for: • Deployment of firmware for single or one-to-many HP ProLiant and HP Integrity servers and network-based targets such as iLO, OA, and VC Ethernet and Fibre Channel modules.
Operating systems and devices HP SUM deployment The following table describes which operating systems run HP SUM, and to which nodes HP SUM can deploy updates. HP SUM runs on/Deploys Windows4, 6 to Firmware Linux4, 6 Software Firmware Software VMware ESXi/vSphere4 HP-UX5 Firmware Firmware 1 Software 2,3 Software Windows Yes Yes Yes Yes Yes N/A Yes N/A Linux N/A N/A Yes Yes Yes1 N/A Yes2,3 N/A Offline SPP Yes N/A Yes N/A Yes N/A N/A N/A 1. 2. 3. 4. 5. VMware ESXi 5.
• Chrome version 24 or later • Screen resolution of 1024 x 768 Supported host operating systems HP SUM supports running on the following operating systems: • Windows 2008, Windows Server 2008, and Windows Server 2008 R2 • Windows 2012, Windows Server 2012, and Windows Server 2012 R2 • Red Hat Enterprise Linux 5.x • Red Hat Enterprise Linux 6.x • SUSE Linux Enterprise Server 10.x • SUSE Linux Enterprise Server 11.
NOTE: Components also have dependencies which need to be met. HP SUM may not be aware that there is a missing library dependency until it attempts to deploy the component. This may occur for a limited number of cases. If you view a Return Code = 7 error in the component log file, you are likely running on a 64-bit Linux operating system and don’t have the required 32-bit dependencies on your system.
Windows • WLDAP32.dll • OLEAUT32.dll • RPCRT4.dll • KERNEL32.dll • USER32.dll • SHELL32.dll • ole32.dll • ADVAPI32.dll • WS2_32.dll • GDI32.dll HP-UX • /usr/bin/swlist • /usr/bin/swinstall VMware ESXi and VMware vSphere operating systems You can update servers running VMware ESXi 5.0 or VMware vSphere 5.1 and later operating systems remotely while running HP SUM on a Linux or Windows system. HP SUM only supports updating firmware for VMware nodes.
Prerequisites for using Linux and HP-UX root credentials If you run HP SUM from a Linux system where you have not logged into the system as a root user, you can still update nodes if you use sudo or super user Access level options. • If you have run HP SUM as a root user, remove the temp directory created by HP SUM. • Make sure you have read/write access permissions to the /tmp and /var directories. • If you create a sudo user, make sure that you add that user to the /etc/sudoers file.
Table 1 HP SUM Windows network ports (continued) Ports Description Ports 445 and 137/138/139 (Port 137 is used only if you are using NetBIOS naming service.) Connects to the remote ADMIN$ share on node 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 node server, you have the correct ports open. Port 5989 This port is used for VMware WBEM discovery.
1. Navigate to the hpsum.ini file in the temp directory, %temp%\HPSUM (Windows) or /tmp/ HPSUM (Linux). NOTE: HP SUM creates this directory the first time you launch HP SUM. If you have not launched HP SUM, launch it and then shut it down. 2. 3. 4. Open the file in a text editor, and edit the following items in the [HTTP] section. • port=63001 edit to port=80 • ssl_port=63002 edit to ssl_port=443 Save the file. Launch HP SUM. It now uses the 80 and 443 ports.
Fixes The following fixes are in this version of HP SUM: • Fixed dependency processing for Linux RPMs, including proper handling of the hp-nx_nic-tools dependency for HP QLogic nx-nic drivers. • Legacy CLI mode fixes • ◦ Fixed error handling with Virtual Connect firmware deployment. ◦ Fixed the issue when HP SUM lost the location of components and no updates occurred. HP SUM runs correctly from mounted devices.
3. Click on the file that you want to download: • HP Smart Update Manager ISO – The HP SUM ISO contains HP SUM and a bootable ISO environment. Firmware and Software components can be added to create a customized baseline. • HP Smart Update Manager RPM – The HP SUM RPM is a native package for Linux and is also available on the Software Delivery Repository at http://downloads.linux.hp.com/SDR/ project/hpsum/.
Downloading HP SUM from the SDR website You can download HP SUM as an RPM from the HP Software Delivery Repository at http:// downloads.linux.hp.com/SDR/project/hpsum/. The SDR contains a version of the HP SUM RPM for each supported operating system and architecture type. Instructions on how to set up your yum configuration are available on the SDR website. You can use yum commands to search for HP SUM and download it to your system.
NOTE: If you are running HP SUM from an ISO that contains updates, the directory might contain a large number of files. Online vs offline mode Mode Uses Online The installation occurs while the host processor is running in the normal server environment. For example, if the server runs Microsoft Windows Server 2012, the update occurs under this environment. The update does not require you to boot to a special environment to update the firmware. You might need to reboot the node to activate the firmware.
3. 4. Activate TFTP within XINETD. • Change disable=yes to disable=no in /ect/xinet.d/tftp • Restart XINETD Set up the PXE server to use a static IP: a. Create the file /ect/sysconfig/network-scripts/ifcfg-eth0.static b. Set the contents to the file as: DEVICE=eth0 BOOTPROTO=STATIC ONBOOT=no TYPE=Ethernet IPADDR= NETMASK= GATEWAY= 5. Set up the PXE boot environment: a. Copy initrd.
7. Create a default pxelinux configuration. a. Create a file name default in the /tftpboot/pxelinux.cfg directory. b. Set the contents of the default file to: prompt 1 default Linux timeout 100 label Linux kernel vmlinux append initrd=initrd.img ramdisk_size=9216 noapic acpi=off 8. 9. Copy the entire contents of the SPP ISO to a directory named /tftpboot/SPP*, where ‘”’ represents the version of the SPP. Add the following to /ect/httpd/conf/httpd/conf where “*” represents the version of the SPP.
Migrating nodes from HP SUM 5.x to HP SUM 6.x HP provides scripts that migrate the targets you added to HP SUM 5.x into nodes that HP SUM 6.x recognizes. If you want to edit the targets that you migrate to HP SUM 6.x, use the /script parameter. This generates a file that you can edit with a text editor application. NOTE: The migration script does not support sudo credentials. To migrate nodes to HP SUM 6.x: 1. Navigate to the directory that holds HP SUM. 2. Double-click port_targets.
3. 4. When running HP SUM on Windows, if the iLO Channel Interface Driver is not installed, the iLO FW will show a version of 'None' as the installed version and 'Ready for Installation' as the status on the Select Bundle or Select Component page. This applies to firmware for iLO 2, 3, and 4. When you try to update the firmware, it might not update if it is already up to date. Broadcom NICs are not discovered by HP SUM unless the appropriate driver is installed and all Ethernet ports are up.
Suggested Action: You can ignore the warning, but HP recommends updating to HP SUM 6.3.1 or later if you encounter this warning. HP SUM includes a newer certificate that does not display this warning. HP SUM does not start on ports lower than 1024 if you use the /port or /ssl_port parameters Suggested Action: Use the following instructions to work around the issue: 1. Navigate to the hpsum.ini file in the temp directory, %temp%\HPSUM (Windows) or /tmp/ HPSUM (Linux).
Some screens are not translated from English Suggested Action: No action. This is a known issue that will be fixed in a future version. HP SUM might start deploying updates when you click the Analysis button Suggested Action: Click Abort to cancel deployment. This issue will be resolved in a future version. HP SUM displays the message “Generating Report” after you click the Analysis button Suggested Action: No action necessary. This will be fixed in a future version.
Node issues HP SUM does not support DNS names with a dash (-) in the name Suggested Action: Do not use a dash in the DNS name. This will be resolved in a future version. HP SUM displays an incorrect message, “Generating Report” when analyzing multiple nodes Suggested Action: Re-analyze the nodes that did not analyze correctly. This will be fixed in a future version. HP SUM adds the same node twice if the node has IPv4 and IPv6 addresses Suggested Action: No action.
HP SUM displays an error when it inventories WBEM and FCHBA components on VMware nodes Suggested Action: No action. This indicates that the VMware WBEM provider might be stopped or hung. HP SUM displays “Update returned an error” when deploying the HP ProLiant Converged Network Utility for Windows 2008 (component cp022111.exe) Suggested Action: No action. This will be resolved in a future version. HP SUM stops responding when it attempts to deploy component cp020538.exe Suggested Action: No action.
HP SUM does not add all associated nodes when a firewall is enabled on Windows 2012 and Windows 2012 R2 operating systems Suggested Action: Make sure you shut down firewalls before adding additional nodes. HP SUM does not downgrade a VC node to version 4.1 Suggested Action: HP SUM 6.x support downgrading VC firmware to version 3.75. HP SUM does not add nodes if the node’s IPv6 address is on a link local network Suggested Action: HP SUM does not support IPv6 link local addresses.
Suggested action: HP SUM is unable to open the firewall in all instances. These include: third-party firewall applications, Linux iptables DROP entries, and firewalls with complex rules. When the open_firewall command does not work, manuallyopen the firewall and then HP SUM can manage the node. HP SUM does not deploy IPDU nodes if the same version of the firmware is already installed Suggested action: No action. This will be resolved in a future version.
HP SUM does not present some RPMs for deployment even if they apply to the node Suggested Action: Some RPMs do not contain the appropriate data for HP SUM to present them for deployment. You can deploy these RPMS outside of HP SUM. The required data will be updated in a future version of the RPM. Advanced filters do not work as expected when you create a custom baseline Suggested Action: No action. This will be resolved in a future version.
HP SUM does not process baselines which include special characters, for example ( Suggested Action: If HP SUM does not recognize a baseline directory path, remove special characters. This will be resolved in a future version. Component issues iPDU node components do not display the Force option Suggested Action: HP SUM does not support downgrading or rewriting components for an iPDU node. HP SUM 6.
HP SUM updates do not complete and display the message Not updated - already current Suggested Action: Do not use the Force command or parameter to update NIC firmware. CLI issues The /use_web legacy CLI command does not work Suggested Action: Use the GUI mode to download baselines from hp.com. Once HP SUM downloads the baseline, you can use CLI mode to perform updates using the downloaded baseline.
HP SUM displays the session ID, not the node name, on the Activity screen when generating a report Suggested Action: No action necessary. This will be fixed in a future version. HP SUM does not include the correct number of components in a baseline from the HP website in an Inventory report Suggested Action: No action. This will be resolved in a future version. Help issues HP SUM does not support the node parameter for input files Suggested Action: Do not use the node parameter for input files.
