Smart Update Manager Release Notes

Transcription

1 Smart Update Manager Release Notes Version Abstract This document describes release information about this version of SUM. This document is intended for individuals who understand the configuration and operations of Microsoft Windows, Windows Server, Linux, smart components, VMware, and the risk of data loss from performing updates. Part Number: a Published: August 2017 Edition: 2

2 Copyright 2012, 2017 Hewlett Packard Enterprise Development LP Notices The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark of The Open Group. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Open source tools OpenPegasus version : Mongoose version 3.2: open-wsman zlib version : version 1.2.8: libcurl version : gsoap version : libssh2 version 1.4.3: libxml2 version 2.9.1: libxslt version : OpenSSL version 1.0.1s:

3 Cygwin libraries sed.exe version grep.exe version strings.exe version rpm.exe version xorriso.exe version Genisoimage json version sqlite version

4 Release Notes Smart Update Manager SUM is a tool for firmware, driver, and software maintenance on ProLiant servers, BladeSystem enclosures, Moonshot systems, and other nodes. It provides a browser-based GUI or a command-line scripting interface for flexibility and adaptability. SUM identifies associated nodes you can update at the same time to avoid interdependency issues. Key features of SUM include: Discovery engine that finds installed versions of hardware, firmware, and software on nodes. SUM deploys updates in the correct order and ensures that all dependencies are met before deploying an update. Interdependency checking. Automatic and step-by-step localhost Guided Update process. Web browser-based mode. Ability to create custom baselines and ISOs. Support for ilo Repository (Gen10 ilo 5 nodes only). Simultaneous firmware and software deployment for multiple remote nodes. Local offline firmware deployments with SPP deliverables. Extensive logging in all modes. NOTE: SUM does not support third-party controllers, including flashing hard drives behind the controllers. Update recommendation Recommended Includes new enhancements, features, and/or minor bug fixes. Hewlett Packard Enterprise recommends all customers to update at their earliest convenience. Supersede information Supersedes: Products This release applies to the following products: SPP and related supplements The minimum SPP version is HPE Moonshot Component Packs The minimum version is HPE Moonshot Component Pack Supported browsers Internet Explorer version 9, 10, or 11 Edge browser: Users must launch SUM using Run as Administrator. Firefox version 17 ESR (Linux) and version 18 (Windows) or later 4 Release Notes

5 Chrome version 24 or later Screen resolution of 1024 x 768 or higher Devices supported Installation of this release allows the following operating systems to then be supported on the product models: SUM runs on/sum deploys to Windows 2, 3 Linux 2, 3 VMware ESXi/vSphere 2 Firmware Software Firmware Software Firmware Software Windows Yes Yes Yes Yes Yes 1 Yes 1 Linux N/A N/A Yes Yes Yes 1 Yes 1 Offline SPP Yes N/A Yes N/A Yes N/A The offline SPP can also deploy firmware to supported hardware, no matter what operating system it normally runs. 1. VMware ESXi 5.0 or VMware vsphere 5.1 and later, SUM and later supports online driver updates for VMware ESXi 5.x and later. 2. ProLiant nodes running a supported OS version. 3. SUM does not support running on IA64 systems. Operating systems SUM is supported on the operating systems listed below. Windows: Windows Server 2012 R2 Windows Server 2016 SUM requires that the admin$ is enabled on Windows systems. For more information on enabling the admin$ share, see NOTE: SUM does not support Windows clustered environments. Remove the server from the cluster system to deploy updates. Launch SUM using Run as Administrator Linux Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 12 Launch SUM as a root user or using sudo for Linux systems. Offline SPP or SUM ISO Devices supported 5

6 IMPORTANT: SUM does not support adding Windows nodes or deploying components to Windows nodes from a Linux host. More Information Prerequisites on page 10 Languages English Japanese Simplified Chinese Enhancements This version of SUM includes the following enhancements: Added support for new ProLiant Gen10 servers and options. Support for ilo 5 repository and install sets Inventory improvements Deploy page enhancements Only deploys HPE-signed components Deploys Clear OS components Baseline improvements Inter-target dependency identification for OA, VC, ilo, SAS Fixes Inventory no longer fails on Gen8 and Gen9 servers when SUM is running. SUM processes passwords that contain and equals = sign. SUM firmware discovery for OA nodes is shorter. SUM firmware report no longer displays HDDs that are not in the system. P220i and P420i Smart Array Control drivers update as expected. SUM inventory does not cause unexpected shutdown on Windows clustered server nodes. SUM updates EFM firmware consistently. Drivers and/or enablement kits must be installed prior to detecting and updating some hardware and firmware Cause You might need to run SUM twice for all firmware components to be presented for installation. This is due to a requirement that drivers are needed for SUM to discover some hardware and thus the needed firmware. After the drivers are installed for the first time and the system rebooted, SUM needs to be run again for all of the firmware components to be presented for installation. 6 Languages

7 Action 1. When performing online updates on a new installation of a supported Windows or Linux OS, all of the appropriate drivers are listed on the Review/Deploy screen but all of the applicable firmware components might not be listed. 2. Network Adapters (NICs), Host Bus Adapters (HBAs), and ilo require a driver or enablement kit to be installed to be recognized by SUM. 3. If the ilo Channel Interface Driver is not installed, the ilo firmware will show a version of CHIF Needed 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. 4. Broadcom NICs are not discovered by SUM unless the appropriate driver is installed and all Ethernet ports are up. To bring up Ethernet port, use the following command: # ifup ethx or # ip link set enox up 5. To update the firmware for Broadcom NIC, use the following steps: a. Install the appropriate Windows or Linux driver found in the SPP. If updating a Linux server, the driver can also be retrieved from the SDR or the Linux distro. b. Enable all the Ethernet ports. c. Run the Broadcom FW upgrade component. SUM deployment fails on ilo 5 Cause Action SUM deployment fails on an ilo 5 node and reports that SUM cannot save the install set in offline mode. TPM is enabled on the node. 1. Disable TPM. 2. Relaunch SUM and then update the node again. SUM does not detect older Smart Array controllers Action SUM does not detect older Smart Array controllers and displays return code 3 1. On Red Hat Enterprise Linux 7.1 and later systems, run the command modprobe sg to load the sg driver. After the loading the sg driver, /dev/sg devices can access SCSI devices. SUM displays the error message Multiple connections to a server or shared resource by the same user... User sees the error message Multiple connections to a server or shared resource by the same user... SUM deployment fails on ilo 5 7

8 Cause Action SUM uses the admin$ share function on Windows-based servers to copy files and perform required operations on remote node servers. If SUM detects multiple connections to the remote Windows node, it might display Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. 1. Open a command prompt window. 2. Enter net use. 3. If the command returns open connections on the remote node, enter: 4. net use <node_admin_share> /delete 5. Retry the operation in SUM that caused SUM to display the error. Updating the HPCISSS2 and HPCISSS3 drivers Action Confusion about which driver to install. 1. If you are updating the Smart Array SAS/SATA driver, use the following table to determine which driver SUM installs if you select both the HPCISSS2 and HPCISSS3 drivers on the Review/Deploy screen: Installed driver version CISSS2 CISSS3 HPSAMD driver HPCISSS2 driver HPCISSS3 driver Installs if only this driver is selected. Installs and updates. Installs CISSS3 if both drivers were selected. Installs and updates. The open_firewall command does not work on some nodes Action On some nodes, SUM launches and adds nodes, but fails when you inventory a node. 1. 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, manually open the firewall and then SUM can manage the node. gatherlogs and clean-cache do not work if you are running SUM with a non-default temp directory path gatherlogs and clean-cache do not work if you are running SUM with a non-default temp directory path. 8 Updating the HPCISSS2 and HPCISSS3 drivers

9 Action 1. Manually zip or tar the non-default temp directory when needed instead of using gatherlogs. Manually erase the non-default temp directories instead of using clean-cache. SUM page refreshes in Internet Explorer 11 unexpectedly Cause Action SUM page refreshes in Internet Explorer 11 unexpectedly This is a known issue with Microsoft Internet Explorer For information on how to resolve this issue, see the Microsoft web page at: support.microsoft.com/en-us/kb/ SUM does not display BIOS firmware RPM deployments as requiring a reboot Action If the BIOS firmware is the only component that requires a reboot, SUM does not automatically reboot the node. 1. Manually reboot the updates nodes. SUM does not display RPM components correctly Cause Action SUM displays one of the following with a firmware RPM component: Baseline inventory lists a firmware RPM as a software or driver RPM. The deployment screen only displays software or driver components. The baseline screen does not show the component configuration link. Inventory fails for Virtual Connect components on Linux nodes. The absolute path for the baseline includes a space. 1. Remove the baseline from SUM. 2. Shut down SUM. 3. Remove empty spaces from the directory absolute path. 4. Run clean-cache. 5. Launch SUM, add the node and baseline, and perform the udpates. SUM page refreshes in Internet Explorer 11 unexpectedly 9

10 SUM inventory fails if the remote system is in a different domain Action SUM inventory fails if the remote system is in a different domain. 1. Make sure that the user account on the local host running SUM has administrator privileges on the remote domain and node. SUM cannot unzip a component Action SUM cannot unzip a component. 1. SUM requires the Linux utility unzip. SUM displays unexpected components for deployment Action SUM displays components that do not apply to a node. cp exe displays for Gen10 servers. 1. Manually de-select the component so it is not deployed. Prerequisites 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. Make sure that there is at least: 1 GB of free disk space available for SUM for temporary files. 100 MB free memory to launch SUM. SUM uses language settings on the host system to determine which language it displays. IMPORTANT: SUM requires the 32-bit libraries to run on 64-bit Linux platforms. Dependencies for specific components exist that might differ from the SUM requirements. To view the dependency summary, use the command #rpm -qipr sum-8.x.x-xxx.x86_64.rpm. 10 SUM inventory fails if the remote system is in a different domain

11 Windows operating system dependencies WLDAP32.dll OLEAUT32.dll RPCRT4.dll KERNEL32.dll USER32.dll SHELL32.dll ole32.dll ADVAPI32.dll WS2_32.dll GDI32.dll NETAPI32.dll IPHLPAPI.DLL SETUPAPI.dll dbghelp.dll Secur32.dll MPR.dll VERSION.dll WINMM.dll admin$ is enabled Linux operating system dependencies and utilities The following Linux utilities need to be installed on the system running SUM and the node you are updating: Operating system dependencies libcrypt.so libcrypt.so.1 /usr/lib/libqlsdm.so /usr/lib64/libqlsdm-x86_64.so /lib/cim/libqlsdm.so /usr/lib/libemsdm.so /usr/lib64/libemsdm.so /lib/cim/libemsdm.so /usr/lib/bfahbaapi.so /usr/lib64/bfahbaapi.so /lib/cim/bfahbaapi.so linux-vdso.so.1 /lib64/libpthread.so.0 /lib64/libz.so.1 /lib64/libdl.so.2 /lib64/librt.so.1 /usr/lib64/libstdc++.so.6 /lib64/libm.so.6 /lib64/libgcc_s.so.1 /lib64/libc.so.6 /lib64/ld-linux-x86-64.so.2 Required Linux utilities coreutils Windows operating system dependencies 11

12 cut ls rm uname cat chmod chown nohup stat su echo mkdir find mv mknod kcmodule reboot cd exit shutdown df wc id dirname mkisofs Required for creating custom ISO images for legacy (BIOS) nodes. xorriso Required to create ISO images for UEFI nodes. sed rpm bash util-linux kill killall shutdown module-init-tools(lsmod) pciutils(lspci) gawkawk grep sambantim_auth uuidd procps dmidecode ipmitool sudo Required to use sudo credentials for remote nodes. model dirname sysdiscovery_linux.cpp nohup df GNU Dev Tools strings 12 Release Notes

13 ldd ldconfig rpm2cpio Required for extracting the RPM package files. cpio Required for extracting the RPM package files. unzip IMPORTANT: If you are updating a VC or OA node, make sure the required 32-bit libraries are installed on the system running SUM. For more information about the required components, see the Service Pack for ProLiant Components Notes. Updating VMware remote host firmware SUM does not run on VMware. You can update servers running VMware ESXi 5.0 or VMware vsphere 5.1 and later operating systems remotely while running SUM on a Linux or Windows system. SUM supports updating firmware and drivers for VMware nodes. The SPP contains the latest released firmware. For recommended driver and firmware versions for ProLiant servers running VMware ESXi 5.0 or VMware vsphere 5.1 and later, see the VMware firmware and software recipe available on the Hewlett Packard Enterprise Online Depot, available at vibsdepot.hpe.com. For information on the firmware updates available in the SPP, see Service Pack for ProLiant Release Notes. The SPP and later releases include Hewlett Packard Enterprise and third-party drivers that Hewlett Packard Enterprise includes in the Hewlett Packard Enterprise Custom Image. You can update servers running VMware ESXi 5.0 or VMware vsphere 5.1 and later operating systems remotely while running SUM on a Linux or Windows system. You cannot execute SUM locally to update a VMware ESXi or VMware vsphere node. The following must be true to update a VMware vsphere node: To update a node in online mode, you need to install the full WBEM providers. You can update the nodes in offline mode from a bootable ISO without installing the WBEM providers. You cannot deploy drivers in offline mode. The node must be running VMware ESXi 5.0 or VMware vsphere 5.1 and later. The node must be active on the network so that SUM can detect it. The VMware server must be running hp-smx-provider or later. Download the providers for the appropriate version of VMware vsphere release from one of the following locations: Version and later of the HPE Insight Management WBEM Provider offline bundle. You can download the bundle from the Hewlett Packard Enterprise Online Depot at vibsdepot.hpe.com. Version 5.25 and later of the Hewlett Packard Enterprise Custom Image includes the provider. You can download the Hewlett Packard Enterprise Custom Image ISO from the Custom VMware Image for ProLiant Servers website at You are running SUM on a Windows or Linux host computer. NOTE: You cannot execute SUM locally to update a VMware ESXi or VMware vsphere node. Linux root credentials for remote nodes You can provide root credentials, a user with sudo permissions, or provide non-root and root credentials for remote nodes. Prerequisites for using Linux sudo credentials Provide one of the following: Updating VMware remote host firmware 13

14 Username and password Username and SSH key file path (in PEM format) Give the sudo users write access to the /var/tmp directory. For sudo users, add the user to the /etc/sudoers file. The following shows the privileges and specifications for users. User: Root Privilege: ALL=ALL Specification: ALL User: Sudo_user Privilege: ALL Specification: ALL Edit the entry in the /etc/sudoers file so the system asks for the sudo user password instead of root user password when you run the sudo command. The following shows the privileges to comment or remove from /etc/sudoers. User: ALL Privilege: ALL Specification: ALL NOTE: Only use this option with Defaults targetpw on all systems. To use super user functionality, configure the user as a super user with all root privileges. You can also use non-root user with a root user to update components. When using SSH keys for login credentials combined with sudo, edit the entry in the /etc/sudoers file so that the system does not ask for the user password as follows: User: sudo_user Privilege: ALL Specification: NOPASSWD:ALL Using an SSH keyfile with root credentials Procedure SUM allows you to log in with a password or by providing an SSH key. 1. On the node that is running SUM, type ssh-keygen -t rsa. SUM also supports DSA encryption key format. To create a DSA encryption key, type ssh-keygen -t dsa. A passphrase is optional. 2. Save the key in the directory.ssh/id_rsa.pub. Root users, use the directory /root/.ssh. 3. Verify that the private key is in PEM format by opening the key and viewing the top of the key for the following text: ---- BEGIN RSA PRIVATE KEY If necessary, on the node you want to update, create an.ssh directory at the root level. Set the permissions level on the directory to Determine if the node you want to update has the filename.ssh/authorized_keys. If this file is not present, create or append this file. Set the permissions on the authorized_keys file to Using an SSH keyfile with root credentials

15 NOTE: If you append the file, more users are authorized to use the private key. 6. Copy the contents of.ssh/id_rsa.pub on the host node, and then paste them into the filename.ssh/authorized_keys on the remote node. 7. Open an SSH path between the host node and the node you want to update. a. Type ssh This parameter opens a shell path. b. Type ssh root@ uname. This parameter executes the command and returns. 8. SUM requires access to id_rsa (private key file), and the optional passphrase. NOTE: If other applications require the public key in PEM format, you can convert it by typing sshkeygen -e -f id_rsa.pub > id_rsa_pub.pem. Open the key, and look at the PEM format for ---- BEGIN SSH2 PUBLIC KEY To create a private key on a Windows system, you can use an application like PuTTY or PuTTY Key Generator (PuTTYGen). For more information, see how-to-create-ssh-keys-with-putty-to-connect-to-a-vps. To export the file to PEM format, select, Conversion > Export OpenSSH key. SUM network ports used SUM requires that certain network ports are available. If you lock down network ports, make sure that the ports listed in the network port tables are open so that SUM works correctly when connecting to remote node servers and hosts. If you are unable to unlock these network ports, you must run SUM locally and update network-based hosts through their web interfaces (for example, the OA, ilo, and VC modules). NOTE: Use the open_firewall parameter for SUM to automatically open the required firewall ports on the local host and any remote servers. Updates for most node types require network traffic in both directions between the server running SUM and the node. The server running SUM creates a local HTTP server, which is used to serve firmware binaries to the node and to communicate node status. The remote node issues HTTP requests and posts status updates to the server running SUM during the update process. If there is a routing problem or firewall blocking traffic back from the remote node to the system running SUM, firmware updates might be blocked, status updates blocked or delayed, or both. After creating the initial communication binds to one of the available ports, SUM traffic can move to a dedicated high-number port number (greater than 1024). This frees up the initial port for new requests. System running SUM Target node type Inventory phase Deployment phase To target From target (SUM and later) To target From target (SUM and later) Windows Windows 445, 135, 137, 138, 139 None 445, 135, 137, 138, 139 None Table Continued SUM network ports used 15

16 System running SUM Target node type Inventory phase Deployment phase Windows or Linux Windows or Linux Windows or Linux Linux 22 None 22 None VMware 443, , OA 22, (80), 443 None 22, (80), 443 None Windows or Linux Windows or Linux Moonshot, Superdome X ilo, VC, FC switch, SAS switch 22, (80), 443 None 22, (80), , , (80), 443 None 22, (80), SUM uses port to communicate between the sum_binary and sum_service applications on both Windows and Linux systems. If ports are listed in both columns, SUM communicates bidirectionally. NOTE: Windows to Windows traffic uses WMI, a standard DCOM-In port 135 and Async-in and WMI-in. Issue the commands /port and /ssl_port to change from ports and if there are firewall conflicts. Use --open_firewall to open the HTTP and HTTPS ports used by SUM for external access. Open these ports for remote node functionality and for remote browser access. For example: smartupdate /port 80 /ssl_port 443 You can issue the command /ftp_port to assign which port to use for FTP service. By default the FTP port is disabled. Use the command to enable the service. Changing the port address in the.ini file You can change the network ports SUM uses by editing the sum.ini file or using the /port or /ssl_port CLI parameters. For more information on using SUM CLI mode, see Smart Update Manager CLI Guide. Procedure The following commonly used alternate network ports are: 1. port=63001 edit to port= ssl_port=63002 edit to ssl_port=443. Component dependencies In some cases, SUM might not detect that there is a missing library dependency until it attempts to deploy the component. If you see 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. ilo Channel Interface Driver Before SUM can determine the firmware version on an ilo node, you have to install the ilo CHIF drivers. For more information, see the ilo 4 User Guide at 16 Changing the port address in the.ini file

17 For Linux nodes, the name of the ilo CHIF driver is hpilo.ko. Supported Linux distributions include the kernel module. Installation instructions SUM is delivered with each SPP, Integrity update bundle, or as a stand-alone ISO. SUM requires no installation. You only need to download SUM to a supported server, and then launch it. You can download the latest version of SUM from the SUM download website at Files included in the SUM download Download SUM from the Hewlett Packard Enterprise website or from the Software Delivery Repository as a standalone application. The standalone application does not include updates for your environment. You can obtain update components from the SPP, SPP Custom Download, or from the SDR. The SUM download includes the following: smartupdate SUM runs in either GUI, interactive CLI, CLI, or Linux RPM mode. By default, SUM opens in the GUI version. If you enter smartupdate /s, SUM runs in the CLI mode. If you enter smartupdate and one of the interactive CLI commands, SUM opens in interactive CLI mode. clean-cache Removes the files in the temp directory associated with SUM that contain cached information about nodes and baselines. Logs are still maintained. gatherlogs Collects all logs for SUM. The logs are useful when debugging or troubleshooting issues for SUM. sum_migration Migrates node data from earlier versions of SUM to the current version of SUM. Prerequisites are available in the Smart Update Manager Release Notes available at support/sum-rn-en. Downloading SUM from the Hewlett Packard Enterprise website Procedure 1. Launch a web browser. 2. Go to 3. Click the file that you want to download: a. Smart Update Manager The ISO contains SUM and a bootable ISO environment. Firmware and Software components can be added to create a customized baseline. b. Smart Update Manager RPM The RPM is a native package for Linux and is also available on the Software Delivery Repository at c. Smart Update Manager zip The zip file contains the files for running SUM on supported Windows and Linux operating systems. Downloading SUM from the SDR website You can download SUM as an RPM from the Software Delivery Repository at support/sdr-sum. The SDR contains a version of the SUM RPM for each supported operating system Installation instructions 17

18 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 and download SUM to your system. You can also use a web browser to navigate the SDR and download the rpm. Use the following commands to search, download, or install SUM from the SDR: yum search smartupdate Search for SUM with yum. yum install smartupdate Install SUM with yum. rpm -Uvh sum-<version>.<os>-<os_version>.x86_64.rpm Download SUM from the SDR with a web browser, and then install the RPM. For more information on using the SDR, see the Getting Started and FAQ sections on the Software Delivery Repository website at For more information on using SUM with the SDR, see Linux best practices document at Launching SUM If you downloaded SUM as a standalone application, the ISO, zip, or RPM does not include software, driver, or firmware components. You can download components from If you downloaded SUM as part of an SPP bundle release, the download includes component updates. When you launch SUM from a mounted ISO, such as ilo Virtual Media, SUM creates a local copy of the SUM binaries.%localappdata%\localsum (Windows) or /var/tmp/localsum (Linux) directory. Delete the temporary localsum files manually because the clean-cache command does not clean these files. SUM displays messages about copying files to the drive specified. If you run SUM on a fileshare directory, SUM does not need to copy the files if you run. NOTE: When you launch SUM on a Windows node, the CHIF driver is installed automatically. To skip installing the CHIF driver, use the /skip_prereqs parameter. SUM cannot connect to an ilo 5 node without the CHIF driver. Gen10 servers require the CHIF driver. Gen9 and older servers do not require the CHIF driver to communicate with SUM, but the CHIF driver allows SUM to determine all component versions. Windows 2012 and later: Add the system to the domain and use the Domain Admin group user. IMPORTANT: SUM does not support multiple users logging in to SUM at the same time. All users must have administrator privileges, or the equivalent, for all nodes you are updating. Each time you launch SUM it determines the state of each node that it manages. SUM determines changes that might have happened between sessions. Procedure 1. Navigate to the directory where you saved SUM. 2. Do one of the following: 18 Launching SUM

19 GUI mode Navigate to the directory where you saved SUMSUM. To launch SUM on a fileshare directory, enter the command smartupdate.bat (Windows) or smartupdate.sh (Linux). To launch with a specific debug directory, use smartupdate /debuglogdir <debug_directory_path> Text-based console mode (interactive CLI) Navigate to the directory where you saved SUM. From the command line, type smartupdate and a console parameter. For a full list of parameters, type smartupdate -h (Linux) or smartupdate /h (Windows). CLI mode and Input file mode Navigate to the directory where you saved SUM. Type smartupdate /s /h Windows and smartupdate -s -h (Linux) for a full list of parameters. If you are using an input file, include the directory path to the input file. For full details on using SUM in CLI mode, see the Smart Update Manager CLI Guide. Launching SUM in GUI mode from an ISO Run SUM on a Windows or Linux operating system. NOTE: When you launch SUM on a Windows node, the CHIF driver is installed automatically. To skip installing the CHIF driver, use the parameter /skip_prereqs. Procedure 1. Copy the files from the ISO to your local host. 2. Run launch_sum.bat (Windows) or launch_sum.sh (Linux) from the directory that contains the ISO. NOTE: If you are using Gnome Virtual file system, manually extract the ISO and save them in a directory. Then launch SUM. SUM and SPP Boot environment change The USB Key Utility does not support multi-boot setups on a single device, for example a USB key. SUM and SPP ISOs contain signed parts to work with the UEFI bootloader. Running SUM in online or offline mode Procedure 1. Online mode 2. Offline mode Running SUM in offline interactive or automatic mode from an ISO with updates If your ISO contains updates, you can copy the ISO to a DVD or USB key. From the DVD or USB key, you can run SUM in an offline interactive or automatic mode. Procedure 1. Automatic mode Launching SUM in GUI mode from an ISO 19

20 Firmware components update without interaction. To launch automatic mode: a. Install the DVD or USB key into the server, boot the server to the DVD or USB key. b. SUM launches and deploys updates after a short period. 2. Interactive offline mode Allows you to use the GUI mode to deploy updates. To launch offline interactive mode: a. Install the DVD or USB key into the server, boot the server to the DVD or USB key. b. Press a key to launch SUM in offline interactive mode. Launching SUM from the RPM Procedure 1. From any directory, type smartupdate. Using a PXE server to deploy updates Procedure Use these steps to set up a PXE server on a Linux system. 1. Install the following packages: a. tftp-server b. dhcp c. httpd d. syslinux 2. Set up a DNS server on your network. Although not required, Hewlett Packard Enterprise recommends setting up a DNS server. 3. Activate TFTP within XINETD. a. Change disable=yes to disable=no in /etc/xinet.d/tftp b. Restart XINETD 4. Set up the PXE server to use a static IP: a. Create the file /etc/sysconfig/network-scripts/ifcfg-eth0.static b. Set the contents to the file as: DEVICE=eth0 BOOTPROTO=STATIC ONBOOT=no TYPE=Ethernet IPADDR=<IP> NETMASK=<IPMASK> 20 Launching SUM from the RPM

21 GATEWAY=<GATEWAYIP> 5. Set up the PXE boot environment: a. Copy initrd.img and vmlinuz from the /system directory of the SPP ISO to /tftpboot directory of the PXE system. b. Copy pxelinux.0 (PXE boot Linux kernel) to the /tftpboot directory. c. Ensure the files copied to /tftpboot are world readable. 6. Configure PXELINUX a. Create directory /tftpboot/pxelinux.cfg. b. Create files representing the hex value of the static IP address in the /tftpboot/pxelinux.cfg directory. For example, if the static IP address used is , the hex value is C0A800FE and the files to be created would be: C C0 C0A C0A8 C0A80 C0A800 C0A800F C0A800FE c. Create a zero-sized file (using touch) representing the MAC address of the NIC of the boot PXE boot client (pre-pended with 01 and replacing : with - ) in the /tftpboot/pxelinux.cfg directory. For example, if the NIC MAC address were 00:01:02:03:04:05, a file name would be 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. Copy the entire contents of the SPP ISO to a directory named /tftpboot/spp*, where * represents the version of the SPP. 9. Add the following to /ect/httpd/conf/httpd/conf where * represents the version of the SPP. <Directory /tftpboot/spp*>. Options Indexes AllowOverride None </Directory> Alias /linux /tftpboot/spp* 10. Start the dhcpd and apache services and activate tftp. service dhcpd start service xinetd restart service httpd start 11. PXE boot the servers to begin the update process. Release Notes 21

22 HPE Firmware Pack for ProLiant Updating with the Python script requires access to the Firmware Pack for ProLiant repository. Before using the commands listed below, install the SUM RPM. For more information on setting up a repository, see smartupdate requires Lists PCI devices currently installed on components. smartupdate list Shows firmware currently installed on the system. smartupdate upgrade Initiates flash engine for firmware packages. smartupdate info Provides detailed description of installed firmware. After establishing a Firmware Pack for ProLiant repository, use the following instructions to download and install the firmware RPMs: Yum install $(smartupdate requires) Press Y when prompted to install applicable RPMs. After the RPMs are installed, type: smartupdate upgrade Press Y when prompted to begin flashing the firmware update to the system. Scaling SUM updates in your environment SUM supports deploying up to 50 nodes at a time in all SUM modes. Deployment times depend on system and server environment variables. NOTE: Update a maximum of 10 VMware nodes at a time. Migrating nodes from older versions to the current version Nodes you added to earlier versions of SUM must be migrated before you can use them in this version of SUM. Use the script sum_migration to perform the migration at any time. Procedure 1. From the SUM directory, launch sum_migration.bat (Windows) or sum_migration.sh (Linux). 2. SUM displays a list of previous versions of SUM it finds. Select the versions you want to migrate to the current version. SUM migrates the node address and name that you have entered in the earlier version of SUM. Related information You can find the latest documentation for SUM in the Smart Update Manager information Library website at Available documents include the following: Smart Update Manager User Guide Smart Update Manager Release Notes Smart Update Manager CLI Guide 22 HPE Firmware Pack for ProLiant

23 To open the Smart Update Manager online help in the GUI, click the? in the upper right-corner of the application. For help using any of the CLI options, see the Smart Update Manager User Guide. You can also type smartupdate /h /s (CLI mode) or smartupdate /h (interactive CLI mode) from the directory where you saved SUM. Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page. Documentation feedback 23