Lifecycle Controller Platform Update in Dell PowerEdge 1 2th Generation Servers This Dell Technical White Paper provides detailed information about the capabilities of Lifecycle Controller to perform firmware updates on Dell’s 12th generation servers.
Learn more Visit support.dell.com/manuals for more information on Lifecycle Controller. © 2012 Dell Inc. All rights reserved. Dell and its affiliates cannot be responsible for errors or omissions in typography or photography. Dell and the Dell logo are trademarks of Dell Inc. Microsoft, Windows, and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Intel and Xeon are registered trademarks of Intel Corporation in the U.S.
Executive Summary Dell regularly releases firmware updates for various server components through the Dell FTP site and SUU DVD. The firmware has new features and fixes for issues. To maximize system performance and avoid unnecessary outages, Dell recommends updating your system with the latest firmware. This whitepaper aims to provide detailed information about the Platform Update feature available in the Lifecycle Controller GUI.
Contents Introduction ....................................................................................... 5 Supported Components ....................................................................... 5 About Platform Update ....................................................................... 6 Platform Update Methods .................................................................... 7 Using FTP Server ..................................................................................
Introduction Lifecycle Controller allows an IT administrator to perform firmware updates and roll backs, and view existing firmware versions even if the operating system is not installed or running. Using Lifecycle Controller, the system can be updated using the repositories accessible through FTP or located on a locally attached USB flash drive, DVD or network share. After selecting the update repository, Lifecycle Controller automatically detects the applicable update.
About Platform Update The following figure provides a snapshot of the Platform Update process. Figure 1.
Platform Update Methods The following table lists the various methods of performing platform update. Table 2.
Figure 2. Select Platform Update The Select Update Repository page is displayed. Figure 3.
3. Select FTP Server as the source location and click Next. The Enter Access Details page is displayed. Figure 4. Enter Access Details 4. In the Address box, type the host name or IP address of the FTP server and click Next: Dell FTP Server (ftp.dell.
The latest firmware is downloaded from Dell FTP server, internal FTP server, or service provider’s FTP server, and the Select Updates page is displayed. Figure 5. Select Updates - FTP Figure 6.
Figure 7. Downloading Catalog Figure 8. Downloading Catalog Signature Figure 9.
5. For a component, compare the currently installed firmware version and the later version under the Current and Available columns. Figure 10. Components (current and available version) 6. Select the required components. NOTE: By default, Lifecycle Controller selects the components for which a later version is available. 7. Click Apply. After the update process is complete, the system reboots. NOTE: When applying more than one update, the system may need to reboot between updates.
Using Proxy FTP Server Lifecycle Controller can be used to perform updates with firmware available at ftp.dell.com, or by using an internal, or service provider’s FTP server when you are connected to the Internet through a proxy server. Before performing the update, make sure the following prerequisites are met: Network settings are configured (Lifecycle Controller Settings Network Settings).
3. Select FTP as the source location and click Next. The Enter Access Details page is displayed. Figure 12. Enter Access Details 4. In the Address box, type the host name or IP address of the FTP server. Dell FTP Server (ftp.dell.com) Internal or service provider’s FTP server (contact your system administrator or service provider for the information) 5. Provide the proxy server credentials and click Next.
Figure 13. Select Updates - FTP Figure 14. Connecting to FTP Figure 15.
Figure 16. Downloading Catalog Signature Figure 17. Verifying Catalog Signature 6. For a component, compare the currently installed firmware version and the later version under the Current and Available columns. Figure 18.
7. Select the required components. NOTE: By default, Lifecycle Controller selects the components for which a later version is available. 8. Click Apply. After the update process is complete, the system reboots. NOTE: When applying more than one update, the system may need to reboot between updates. In this case, the system boots directly into Lifecycle Controller and automatically continues the update process.
Figure 19. Select Update Repository 3. Insert the appropriate DVD in the locally-attached CD/DVD drive. Alternatively, insert the appropriate DVD in the client and use the Virtual Media feature to access the attached CD/DVD drive. For more information, see iDRAC7 User’s Guide. Figure 20. DVD Mapped To the Client Drive 4. Select Local Drive (CD/DVD/USB) as the source location and click Next. The Enter Access Details page is displayed. However, if the catalog is not signed, a warning message is displayed.
Figure 21. Enter Access Details Figure 22.
Figure 23. Warning Message 5. From the Local Drive drop-down menu, select the appropriate drive and click Next. The Select Updates page is displayed. Figure 24.
Figure 25. Select Updates (OS Driver Pack) 6. For a component, compare the currently installed firmware version and the later version under the Current and Available columns and select the required components. NOTE: By default, Lifecycle Controller selects the components for which a later version is available. 7. Click Apply. After the update process is complete, the system reboots. NOTE: When applying more than one update, the system may need to reboot between updates.
To update the platform using USB: 1. Launch Lifecycle Controller: Press key within 10 seconds of the logo being displayed during boot. 2. Click Platform Update Launch Platform Update. The Select Update Repository page is displayed. Figure 26. Select Update Repository 3. Insert the USB flash drive to the host. Alternatively, insert the USB flash drive to the client system and use the Virtual Media feature to access it. For more information, see iDRAC7 User’s Guide. Figure 27.
4. Select Local Drive (CD/DVD/USB) as the source location and click Next. The Enter Access Details page is displayed. Figure 28. Enter Access Details 5. From the Local Drive drop-down menu, select the appropriate drive.
6. Enter the path to the catalog file and click Next. The Select Updates page is displayed. However, if the catalog is not signed, it displays a warning message. Click Yes to continue. Figure 29. Verifying Selection Figure 30.
Figure 31. Select Updates 7. For a component, compare the currently installed firmware version and the later version under the Current and Available columns and select the required components. NOTE: By default, Lifecycle Controller selects the components for which a later version is available. 8. Click Apply. After the update process is complete, the system reboots. NOTE: When applying more than one update, the system may need to reboot between updates.
Using a Network Share (CIFS or NFS) If you are accessing the updates from a CIFS or NFS share, select Network Share. To update the platform using CIFS or NFS network share option: 1. Launch Lifecycle Controller: Press key within 10 seconds of the logo being displayed during boot. 2. Click Platform Update Launch Platform Update. The Select Update Repository page is displayed. Figure 32.
3. Select Network Share as the source location and click Next. The Enter Access Details page is displayed. Figure 33. Enter Access Details - CIFS Figure 34.
4. Select CIFS or NFS, enter the following details, and click Next. Share Name (CIFS or NFS) — Path to the shared folder where the Update Packages or repository is located. For example, \\192.168.20.26\sharename or \\servername\sharename. Domain and User Name (CIFS) — Domain and user name required to log on to the network share. For example, login-name@myDomain. If there is no domain, type only the login-name. For example, login-name. Password (CIFS) — Password to authenticate the user name.
Figure 36. Enter Access Details - NFS Figure 37. Connecting to Network Share Figure 38.
Figure 39. Downloading Catalog Signature Figure 40. Verifying Catalog Signature Figure 41.
Figure 42. Select Updates - CIFS Figure 43.
Creating the Local CIFS or NFS Share Repository If your organization uses a private network that cannot access external sites such as ftp.dell.com, you can provide platform updates from a locally-configured network share device. If a CIFS or NFS share is available, you can copy the repository created using Dell Repository Manager or the repository downloaded from ftp.dell.com.
Figure 45. Warning Message Figure 46. Connecting to FTP Figure 47.
Figure 48. Verifying Update Package Signature Figure 49. Select Updates – Single Component DUP Local Drive (CD/DVD/USB) Download the Dell Update Package (only .exe) from the Dell FTP site (ftp.dell.com), copy from the Server Update Utility DVD, or from support.dell.com. NOTE: If the DUP is located in the root directory, enter the name of the Update Package (for example, APP_WIN_RYYYZZZ.EXE).
Figure 50. Enter Access Details – Local Drive Figure 51.
Figure 52.
Network Share (CIFS and NFS) Download the Dell Update Package (only .exe) from the Dell FTP site (ftp.dell.com), copy the Server Update Utility DVD, or from support.dell.com to a CIFS or NFS network share. NOTE: If the DUP is located in the root directory, enter the name of the update package (for example, APP_WIN_RYYYZZZ.EXE). If the update package is present in a sub-directory, enter both the sub-directory name and name of the update package (for example, subdirectory\APP_WIN_RYYYZZZ.EXE). Figure 53.
Figure 54. Verify Selection Figure 55. Connecting to Network Share Figure 56.
Figure 57. Select Updates – Network Share (CIFS) Figure 58.
Figure 59. Verify Selection Figure 60. Connecting to Network Share Figure 61.
Figure 62. Select Updates – Network Share (NFS) Roll Back to Previous Firmware Version Lifecycle Controller allows roll back to a previously-installed version of component firmware such as BIOS, iDRAC, RAID Controller, NIC, and Power supply. Important The Dell Diagnostics, OS driver packs, and Lifecycle Controller firmware cannot be rolled back to previous versions. The previous version is available only if the component firmware is updated at least once to a different version.
To rollback a firmware version to a previously-installed image: 1. Launch Lifecycle Controller: Press key within 10 seconds of the logo being displayed during boot. 2. Click Platform Update Launch Platform Rollback. Figure 63.
Figure 64. Launching Platform Rollback The Select Components page displays a list of available rollback images with the following details. Component — Displays the available updates. Current — Displays the component version currently installed on the system. Previous — Displays the version number of the previous version.
Figure 65. Platform Rollback – Select Components 3. Select the components and click Apply. 4. Select the rollback image that you want to apply to the system and click Apply. After the rollback process is complete, the system reboots. When applying more than one update, the system may need to reboot between each rollback. In such scenarios, the system boots directly into Lifecycle Controller and continues the rollback process.
To view the currently installed firmware versions: 1. Launch Lifecycle Controller: Press key within 10 seconds of the logo being displayed during boot. 2. Click Platform Update View Current Versions. Figure 66.
Figure 67.
The View Current Versions page displays a list of installed components with the following information: Component Name — Displays the name of the currently installed component. Version — Displays the firmware version currently installed for that component. Date and Time — The time the component was installed in the system, updated, or rolled back. The format is yyyy-mm-dd hh:mm:ss. Figure 68.
To test the network connection: 1. Launch Lifecycle Controller: Press key within 10 seconds of the logo being displayed during boot. 2. Click Platform Update Launch Platform Update FTP Server or Network Share and click Next. The Enter Access Details page is displayed. Figure 69.
Figure 70. Select Test Network Connection – CIFS Figure 71.
3. Specify the FTP Server or Network Share details. 4. Click Test Network Connection. After the test is complete, the Network Connection Report is generated with the following details: Parameters specified in the Network Settings page - Gateway IP and DNS IP. Parameters specified in the Enter Access Details page – Proxy IP (only if you have specified FTP proxy server) and Server IP (FTP address or network share address.) NOTE: The report always displays the IP address of the host name. Figure 72.
Figure 73. Network Connection Report – Network Share Checking the signature Catalog on FTP Server The catalog present on ftp.dell.com is signed with the signature file present in the same location. NOTE: If a catalog is created using Dell Repository Manager, the catalog does not have an associated signature file. On the Enter Access Details page, after you click Next, the following messages are displayed when Lifecycle Controller connects to a repository: Figure 74.
Figure 75. Downloading Catalog Lifecycle Controller attempts to locate the catalog signature file. If the signature file is not present, a warning message is displayed. To continue, click Yes to open the Select Updates page. Figure 76. Warning Message If the sign file is present, it is downloaded and verified. This ensures that updates are performed only for an authenticated catalog. Figure 77. Downloading Catalog Signature Figure 78.
NOTE: As Lifecycle Controller performs a validation against an authenticated signature file and if it detects any signature mismatch, the firmware update does not continue. 5. After the catalog signature is verified, the Available Updates page is displayed. For more information, see Using FTP Server.
Platform Update Mechanism This section provides the background operations that are performed after you do the following tasks: 1. Select the repository location. 2. Select the components and click Apply. Figure 80. Select Updates The system reboots after the update process is complete for a component. However, if multiple components are selected, the system directly boots into Lifecycle Controller and automatically continues the update process for the next component.
Figure 81. Post Update Behavior NOTE: The time taken for each component update has a set limit. The update is completed within this limit. For more information, see Figure 81. Security is important, and the update process is designed to ensure both system and data are protected. The update process uses multiple layers of security validation: External data is temporarily stored in non‐volatile storage.
Trusted Platform Module Warning If BitLocker protection is enabled on your system, updating components such as RAID, BIOS, and NIC requires you to enter a recovery password or insert a USB flash drive containing a recovery key during the next system boot. This situation occurs only if the Trusted Platform Module (TPM) security setting is set to “On with Pre-boot Measurements.” For information on how to set TPM settings, see the BIOS User’s Guide available at support.dell.com/manuals. Figure 82.
Figure 83. Platform Update – Select Updates TPM Warning Figure 84.
Figure 85.
Using Dell Repository Manager Dell Repository Manager (DRM) is an effective Microsoft Windows-based application that simplifies change management tasks. It helps to maintain Dell systems with the latest BIOS, firmware, drivers, and applications. It operates in server and client modes, obtaining updates for both Dell systems and client systems.
