PROMENTUM® ATCA Firmware and Software Update Instructions October 2011 007-03278-0009
Revision history Version -0000 -0001 -0002 -0003 -0004 -0005 -0006 -0007 -0008 -0009 Date May 2008 October 2008 January 2009 March 2009 July 2009 November 2009 August 2010 November 2010 June 2011 October 2011 Description First edition. Second edition. Minor revisions. Third edition. Several updates Fourth edition. Minor updates. Fifth edition. Several updates. Sixth edition. Minor revisions. Seventh edition. Multiple revisions. Eighth edition. Miscellaneous updates. Ninth edition. Multiple updates.
Table of Contents Preface ................................................................................................................................................ 5 About this manual........................................................................................................................................5 What’s new in this manual...........................................................................................................................
Chapter 5: Setting the CPM boot block jumpers ........................................................................... 43 ATCA-4300 and ATCA-4310 CPM ............................................................................................................43 ATCA-4500, ATCA-4550, and ATCA-4555 CPM ......................................................................................44 Chapter 6: Board-level updates for the ATCA-45xx CPM and RTM .............................................
Preface About this manual ATCA systems running Promentum version 3.5.0 or earlier must be upgraded to version 4.0.0 by following the Promentum 3.x to 4.x Firmware and Software Upgrade/Downgrade Instructions. The update instructions in this document can be used only after all system modules have been upgraded from Promentum version 3.x to version 4.0.0.
Preface Related documents • • Promentum 3.x to 4.x Firmware and Software Upgrade/Downgrade Instructions Promentum ATCA Firmware and Software Update Instructions using the Radisys Software Management Framework Notational conventions This manual uses the following conventions BoldText A keyword. ItalicText File, function, and utility names. MonoText Screen text and syntax strings. BoldMonoText A command to enter. ItalicMonoText Variable parameters. Brackets [ ] Command options.
Chapter 1 Introduction to the update process A remote firmware update utility, rfw‐update, is provided with the latest ATCA release. The rfw‐update utility remotely invokes instances of the rsys‐update tool on specified modules for significantly faster and easier updates of firmware and software components. Using rfw‐update, shelf‐ and system‐wide upgrades can be initiated with a single command from one host, such as an external Linux host or an ATCA‐4500 CPM.
Introduction to the update process 1 Overview of the update process Using rfw-update to update one or more Promentum shelves The basic procedure for updating one or more Promentum shelves is as follows. Additional information about each step is provided in this document. 1. Plan the update by reading this document and identifying the products to update. See page 13. 2. Obtain the update bundles from Radisys. See page 17. 3. Prepare the Linux host where rfw‐update will be run. See page 18. 4.
1 Introduction to the update process rfw-update • • • • • • Utility for updating multiple remote modules by invoking rsys‐update on each module Runs on a host that is NOT being updated, such as a CPM or Linux server User supplies a configuration script that specifies the following “upgrade campaign:” • The modules to upgrade, how to access them, and what firmware to install • Optional override of upgrade order and which upgrades are processed in parallel • Optional checks to verify chassis number, slot n
1 Introduction to the update process Components supported by rfw-update ATCA modules typically have a number of firmware and software components that can be updated. These components are programmed into flash devices or logic devices like FPGAs and CPLDs. Some of the devices act as redundant active‐standby pairs that are updated one at a time. Other devices are single, non‐redundant units. The devices in which software and firmware components are stored are referred to as “banks“ in this document.
Introduction to the update process 1 Upgrade support policy This section describes the Radisys general support policy regarding upgrade version compatibilities when upgrading from one ATCA system release version to another. This general support policy outlines which upgrades can be completed without requiring an intermediate step, and which do require an intermediate upgrade step. Undiscovered defects in previous releases may prevent Radisys from meeting these upgrade objectives.
Introduction to the update process • • 1 From a maintenance release from an older minor release series Example: Upgrading ATCA 4.1.1 to ATCA 4.x.x requires an intermediate upgrade step to ATCA 4.2.X first. From a patch release, which requires an upgrade to the next maintenance release Example: Upgrading ATCA 4.1.1.3 to ATCA 4.2.0 requires an upgrade to ATCA‐4.1.2 first. Note: Patch releases are intended to be short‐term releases that are replaced by the next maintenance release.
Chapter 2 Performing an update using rfw-update This chapter describes the use of the rfw‐update remote firmware update utility. Step 1: Plan the update Identify the products you want to update For each Promentum platform, list all installed ATCA modules (except a CPM if it acts as the Linux host for running rfw‐update). For each of the modules, list the slot where it is installed and the connection IP address (for Telnet or SSH access).
2 Performing an update using rfw-update You can print this page and record the module data in this table before running the update: Slot Name IP Address User:Password Connection Type String WARNING! Do not include a CPM that is acting as the Linux host for rfw‐update in the list of modules to update. Instead, update the CPM manually before or after updating all other shelf components. See Chapter 3, Using rsys‐update for single product updates, on page 31.
Performing an update using rfw-update 2 Save your configuration The rfw‐update utility preserves default configurations across updates for the ATCA‐1200, ATCA‐2210, ATCA‐7220, and ATCA‐9100. Configurations are preserved in both banks to retain the existing setup information. Each ATCA software release image contains a list of files to be preserved, and you can generate a custom list to specify additional files within the /etc directory to preserve.
Performing an update using rfw-update 2 For the ATCA‐7220, the rsys‐update utility creates a custom preservation list at /etc/rsys‐ user‐file‐list.cfg during the update process if the file does not already exist. The rsys‐ update utility adds the following ATCA‐7220 configuration files to that custom preservation list: /etc/octeon.conf /etc/fpga/ppm20fpga.conf All files in /etc/octeon Creating a custom preservation list Other files may need to be preserved.
Performing an update using rfw-update 2 Determine which modules require an IPMC FPGA update IPMC FPGA devices should be updated separately using rsys‐update before running rfw‐ update to automatically update the other module components. This separate update is required so the rfw‐update process runs without interruption and does not require manual user intervention.
Performing an update using rfw-update 2 Step 3: Prepare the Linux host Prerequisites The host system that runs rfw‐update must be a Linux host with LAN access to the modules installed in the shelf. The host system must be running Perl version 5.8.5, and specific Linux, Radisys, and Perl RPMs must also be installed. See Getting required packages for the list of required RPMs. All update targets must be accessible from the host running rfw‐update.
Performing an update using rfw-update 2 2. Install the latest RPM packages. a. Locate the .tgz file appropriate for your operating system in the Promentum CD image, as explained in Getting required packages on page 18. Copy the .tgz file to a temporary directory on the Linux host. Choose a path and name that can be easily accessed for the remaining steps. b. Decompress the .tgz file by entering the following command from within the temporary directory: tar ‐xzvf .
Performing an update using rfw-update 2 Step 4: Update IPMC FPGA devices IPMC FPGA devices for modules must be updated separately using rsys‐update before running rfw‐update to automatically update the other module devices. Refer to the product release notes to identify any IPMC FPGA updates. Follow these steps to perform the update: 1. Determine which modules require IPMC FPGA updates by comparing their installed IPMC FPGA version with the latest Promentum software release.
2 Performing an update using rfw-update Step 5: Create a configuration file (conf.rfw) The rfw‐update utility uses a configuration text file to specify which modules should be updated and whether they will be updated in parallel with other modules to save time. The text file can be any name, but it is named conf.rfw in this document. The conf.rfw file contains a list of bundles with URL paths and a list of update targets with Telnet connect strings.
Performing an update using rfw-update 2 Create conf.rfw from samples in the appendix The conf.rfw file can also be created by referring to samples documented in Appendix A, Sample conf.rfw file, on page 78. A simple example is provided for reference and general use, and the detailed example can be used to produce a complete module update list. Compose and verify the configuration file 1. Use a text editor to create a configuration file. Refer to Appendix A, Sample conf.
2 Performing an update using rfw-update Figure 2. Parallel updates using rfw-update Quick connect Update module and verify update Verify bundle access and version SYS-6010 Shelf 1. ATCA-9100 2. ATCA-4500 3. ATCA-4500 4. ATCA-9100 5. ATCA-7220 6. ATCA-9100 7. ATCA-2210 ATCA-5010/5014 8. ATCA-2210 ATCA-5010/5014 9. ATCA-4500 10. ATCA-4500 11. ATCA-9100 12. ATCA-7220 13. ATCA-9100 14.
Performing an update using rfw-update 2 Selecting the update order The order that modules and components are updated is determined by a number of setups. • The update order is controlled in the conf.rfw file to establish phase groups. • The rfw‐update utility uses its own rules to order multiple modules within the phase groups (see Set up phase groups on page 22 for details). • The update order may also be controlled by configuring multiple rfw‐update files to run sequentially.
Performing an update using rfw-update 2 Step 6: Update the AMC-7211 and AMC-7212 The AMC‐7211 and AMC‐7212 are updated as a non‐redundant component as part of the ATCA‐1200 update bundle, or from a CPM host. While the AMC flash is a non‐redundant component, the host support, which is updated at the same time, is not because it resides in the redundant LMP. Consequently, the host support is only updated in the active LMP and not in the redundant LMP.
Performing an update using rfw-update 2 Step 7: Run the rfw-update utility Quick start Follow these steps to verify the system configuration file and update bundles, then run rfw‐ update to automatically update the modules. Important: You must have root account access for rfw‐update to operate properly. 1. Verify the syntax of the configuration file and test connections to each module: rfw‐update ‐‐quick‐check conf.rfw 2. Verify that each target can access the bundles from the module.
Performing an update using rfw-update 2 Examples rfw‐update ‐‐parse‐only conf.rfw Verifies the syntax of a bundle configuration file and shows an overview of the update order. rfw‐update ‐‐quick‐check conf.rfw Verifies the syntax of a bundle configuration file and connects to each target. rfw‐update ‐‐versions conf.rfw Shows the version information for all bundles and modules defined in the conf.rfw file. rfw‐update ‐‐automatic conf.
Performing an update using rfw-update 2 3. Update Module Pass can be run using the ‐‐automatic option.
Performing an update using rfw-update 2 Step 8: Rediscover the shelf Log in to the ATCA‐2210 SCM that is hosting the active Shelf Manager. Access the CLI and enter: platform‐mgmt rediscoverShelf This ensures that the HPI RPT information is in sync with new versions running in the system. Recovering from update problems If you encounter problems with an update, you can usually recover by updating the component from the redundant bank. Use rsys‐update or component update tools from the working bank.
Performing an update using rfw-update 2 Step 9: Update remaining components The following products and components are either not supported by rfw‐update and their updates must be handled separately, or some updates need to be performed manually along with rfw‐update. Instructions for updating these products and components are included with the individual component update files, unless otherwise indicated.
Chapter 3 Using rsys-update for single product updates This chapter describes the rsys‐update utility, with which you can update most components in a single ATCA module with one command. (See note below.) Use rsys‐update to update a module that is not updated by rfw‐update, such as a CPM that acts as the host for running rfw‐update. Table 1 on page 10 lists the components updated by rfw‐update, which invokes multiple instances of rsys‐update during the upgrade process.
Using rsys-update for single product updates 3 rsys-update command options Table 2 on page 32 describes the rsys‐update command options that are used in these update instructions. Table 2. Command options for rsys-update Option Parameters ‐a, ‐‐automatic Description Update and activate firmware in the factory recommended order (update the redundant components). ‐v, ‐‐versions Show version information for all active, standby, and update bundle components.
Using rsys-update for single product updates 3 rsys-update help Two forms of help are available for rsys‐update if an update bundle is specified in the help command. Use the help commands to view the rsys‐update command syntax. Help on retrieving the update bundle When the rsys‐update help command is entered without specifying an update bundle, the utility only gives help on how it can be used to retrieve an update bundle.
Using rsys-update for single product updates 3 Using full path lists If a full path is specified and the tarball file with a file name ending in “.tgz” exists, the tarball bundle contents are extracted into the directory //. The format of the full path is: //rsys‐update/.tgz Using local directories If a directory is used and the update command exists in the update‐bundle directory, the directory is used as‐is and no file is extracted.
3 Using rsys-update for single product updates 4. Update the standby flash bank: rsys‐update ‐‐path // ‐‐automatic This results in a reboot to the standby (newly updated) flash bank. 5. For local management processor (LMP) modules, confirm the new version works correctly: flashver ‐‐secondary 6. Download the update bundle again, since the temporary storage was lost upon reboot. Refer to the previous section for detailed instructions. 7.
Using rsys-update for single product updates 3 Updating the ATCA-7220 DPB BSPs from 1.4.x to 1.5.x To update the ATCA‐7220 DPB from 1.4.x to 1.5.x (SDK 1.7.2 to 1.9), different update procedures are used if the DPB is booted to Linux or to U‐Boot. Booted to Linux If the ATCA‐7220 DPB is booted to Linux, the DPB BSP can be updated using the following command: rsys‐update ‐‐path ATCA‐7220‐1.12.14.1.4_SDK1.9_Octeon1.5‐1‐firmware.
Chapter 4 Updating ATCA-45xx CPMs This chapter describes the installation of RPM packages and the BIOS driver for updating ATCA‐4500, ATCA‐4550, ATCA‐4555, and ATCA‐4580 CPMs. These are the operating systems supported by the ATCA‐4500, ATCA‐4550, and ATCA‐4555 CPMs: • Monta Vista 4, 32‐bit (Monta Vista CGE 4.0 i386) • Monta Vista 5, 64‐bit (Monta Vista CGE 5.0 x86‐64) • Red Hat 5, 64‐bit (Red Hat 5.4 x86_64) • Wind River 2, 32‐bit (Wind River PNE‐LE 2.0 i686) • Wind River 2, 64‐bit (Wind River PNE‐LE 2.
4 Updating ATCA-45xx CPMs See the Promentum Software Guide for more information about RPM packages. Table 3. RPM packages provided with the CPM update bundle RPM package name AMC7212.RH.4500-.rpm Required for the Functional description update process No Provides libraries, utilities, and PCIe drivers for the AMC-7212 on the ATCA-4500, ATCA-4550, and ATCA-4555. amifldrv-.rpm Yes amifldrv-core8-.rpm bioscli2-.rpm biosver-.
4 Updating ATCA-45xx CPMs Table 3. RPM packages provided with the CPM update bundle (continued) RPM package name make-interfaces-.rpm mcli-.rpm mcli-devel-.rpm perl-Expect-.rpm perl-Inline-.rpm perl-IO-Tty-.rpm perl-Net-Telnet-.rpm perl-YAML-.rpm platform-mgmt-.rpm rfw-update-.rpm rsys_cpm_kernel-.rpm rsys_cpm_kernel-bsp-.
4 Updating ATCA-45xx CPMs Table 3. RPM packages provided with the CPM update bundle (continued) Required for the RPM package name Functional description update process rsys-rpc-support-.rpm No Provides RPC-based Ethernet API functions for configuring the Ethernet switch on ATCA products. rsys-rpc-support-devel-.rpm No Provides the libraries and header files for developing applications that use rsys-rpc-support. rsys-rpc-tools-.
4 Updating ATCA-45xx CPMs Installing the BIOS update driver for rsys-update Note: These installation instructions for the BIOS update driver only apply to the ATCA‐4500, ATCA‐4550, and ATCA‐4555 CPMs. Before running the BIOS update, the rsysbflash utility and the proper kernel driver module for the BIOS flash must be installed. The Promentum software release contains the standard kernel driver for the specific operating system.
4 Updating ATCA-45xx CPMs Verifying the BIOS driver Before running rsys‐update, verify the BIOS driver is present by entering this command: rsys‐update ‐‐path / ‐‐versions The ‐‐versions option shows the version for all active, standby, and update bundle components. See rsys‐update command options on page 32 for details.
Chapter 5 Setting the CPM boot block jumpers The boot block for ATCA‐4300, ATCA‐4310, ATCA‐4500, ATCA‐4550, and ATCA‐4555 CPMs is typically write‐protected to prevent accidental overwrites. Depending on the CPM, a jumper needs to be installed or removed from specific header pins to enable updates to the boot block. ATCA-4300 and ATCA-4310 CPM To update the ATCA‐4300 or ATCA‐4310 boot block, install a jumper to enable writes to the FWH boot block.
5 Setting the CPM boot block jumpers Figure 4. ATCA-4310 boot block header location Install boot block jumper here (P6) ATCA-4500, ATCA-4550, and ATCA-4555 CPM To update the boot block for the ATCA‐4500, ATCA‐4550, and ATCA‐4555 CPM, power down the module, and remove the jumper on pins 1 and 2 of header J1. See Figure 5 on page 45.
Setting the CPM boot block jumpers Figure 5.
Chapter 6 Board-level updates for the ATCA-45xx CPM and RTM The ATCA‐4500, ATCA‐4550, ATCA‐4555, and ATCA‐4580 CPMs and their RTMs must be manually updated at the board level, if a custom operating system is used or if the CPM and RTM are installed in a non‐Promentum shelf.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating the BIOS from DOS 1. Copy AFUEFIx64.efi, BIOS.rom, and update.nsh to a USB flash drive and boot into the EFI shell. The files are located in the firmware/bios folder for the OS update bundle. 2. Switch to the file system on the USB flash drive (usually fs0:). fs0: 3. Run the update.nsh batch file to update one bank. rsysbflash BIOS.ROM /p /b /x 4. Reboot the CPM to the updated bank. 5. Run the batch file again to update the remaining bank. 6.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating the IPMI firmware and FPGA for ATCA-4500, ATCA-4550, and ATCA-4555 These firmware upgrade instructions comply with the PICMG HPM.1 specification. The IPMI controller and associated circuitry include a number of upgradable components. Some of these components are upgraded individually, while others are upgraded as a group. You can upgrade the IPMI firmware and FPGA using either the KCS interface or the LAN interface.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating from the LAN (Shelf Manager) Record the IP address of the active Shelf Manager and the IPMB address of the CPM to be upgraded. For the example commands in this procedure, the IP address is 10.100.18.20 and the target module is in slot 10 (IPMB address 0x8C). This information can be obtained by running the fruinfo tool provided in the update bundle package. 1. Verify that LAN connectivity to the Shelf Manager IP address is established: .
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating the IPMI firmware for ATCA-4580 These ATCA‐4580 firmware upgrade instructions comply with the PICMG HPM.1 specification from PICMG. The IPMI controller and associated circuitry include a number of upgradeable components. Some of these components are upgraded individually, while others are upgraded as a group. You can upgrade the IPMI firmware using either the KCS interface or the LAN interface.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating from the LAN (Shelf Manager) Record the IP address of the active Shelf Manager and the IPMB address of the ATCA module to be upgraded. See Appendix B, IPMB and IPMB‐L address mapping, on page 85 to determine the IPMB address. For further details, refer to the specific shelf or carrier documentation. For the example commands in this procedure, the IP address is 10.100.18.20 and the target module is in slot 10 (IPMB address 0x8C).
Board-level updates for the ATCA-45xx CPM and RTM 6 6. The output should be similar to the following: # rsys‐ipmitool hpm upgrade hpm1fw_.img activate PICMG HPM.1 Upgrade Agent 1.0: Validating firmware image integrity...OK Performing preparation stage... Services may be affected during upgrade.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating the CPM FRU 1. From a module or head system with access to the Shelf Manager, verify that these files from the Promentum software release are present: • FRU .bin and .cfg files • fru_update utility • frutool utility • rsys‐ipmitool utility ./rsys‐ipmitool ‐I lan ‐H 10.100.18.20 ‐A none mc info 2.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating the EEPROM for ATCA-4500, ATCA-4550, ATCA-4555 This procedure updates the entire EEPROM for the ATCA‐4500, ATCA‐4550, and ATCA‐4555 CPM, except for the MAC address. Determine the NIC number The NIC (Network Interface Card) numbers for the Base, Fabric, and Front Ethernet controllers need to be determined so they can be used during the EEPROM update.
Board-level updates for the ATCA-45xx CPM and RTM 6 Perform the update 1. After booting the CPM, verify that rsys‐eeupdate.rpm is installed as part of the required packages listed in Table 3 on page 38. The rsys‐eeupdate binary is installed in the /usr/sbin directory. 2. Copy all eep files to the CPM running Linux. The eep files are located on the Promentum software release in the firmware/ethernet folder for your operating system update bundle. 3.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating the EEPROM for ATCA-4580 This procedure updates the ATCA‐4580 EEPROMs except for the MAC address. The rsys‐ eeupdate utility is used to update an Ethernet EEPROM from the Linux command line. The utility and its kernel driver must be installed before the EEPROM update can be performed. Table 5 provides device information for the ATCA‐4580 Ethernet controllers. Table 5.
Board-level updates for the ATCA-45xx CPM and RTM 6 4. Upgrade the appropriate EEPROM using rsys‐eeupdate: # ./rsys‐eeupdate install i s <.
Board-level updates for the ATCA-45xx CPM and RTM 6 ****************************************************************** LSI Corporation SAS FLASH Utility. SASFlash Version 1.20.00.00 (2008.10.31) Copyright (c) 2006‐2007 LSI Corporation. All rights reserved.
Board-level updates for the ATCA-45xx CPM and RTM 6 Wind River 2, 32‐bit • ispVMEmbedded‐.i686.rpm • cpm_ioport_module‐_18cpm.i686.rpm Wind River 2, 64‐bit • ispVMEmbedded‐.x86_64.rpm • cpm_ioport_module‐_hrt1_cfs_v22_grsec_rsys6.x86_64.rpm Make sure the correct packages are used based on your OS and kernel variant. The current legacy FPGA svf file (*.svf) is also needed.
Board-level updates for the ATCA-45xx CPM and RTM 6 Update the legacy SPI flash (update only if the legacy FPGA is corrupted) Note: Update the legacy SPI flash only if the legacy FPGA flash is corrupted during an update. To update the legacy SPI flash, first see Update the legacy FPGA on page 58 for the two required packages based on your OS. The current legacy SPI flash svf file (*.svf) is also needed.
Board-level updates for the ATCA-45xx CPM and RTM 6 Update the RTM MMC firmware Update the firmware using rsys‐ipmitool and the *.hpm firmware image. 1. Run rsys‐ipmitool with the following syntax: rsys‐ipmitool ‐I lan ‐H ‐A none ‐T ‐B 0 ‐t ‐b 7 hpm upgrade activate Example: rsys‐ipmitool ‐I lan ‐H 10.2.113.200 ‐A none ‐T 0x86 ‐B 0 ‐t 0x90 ‐b 7 hpm upgrade upgrade.
Board-level updates for the ATCA-45xx CPM and RTM 6 Customize the RTM FRU data during an update If you need to customize RTM FRU data, the customization can be accomplished during the FRU update process by specifying the ‐‐full option for the updatefru command. rmcpta ‐h targetfwd updatefru backup.
Board-level updates for the ATCA-45xx CPM and RTM 6 Using setdriveinfo The rmcpta setdriveinfo command sets the drive information for the type of hard disk drive installed on the RTM (SAS or SATA). This procedure is needed only if you change the hard disk drive on the RTM. 1.
Board-level updates for the ATCA-45xx CPM and RTM 6 The following list defines the OpenSession command options: • 14 is the IPMI channel number • 4 is the requested privilege level • 2 is the requested authentication type • root is the default username • cmmrootpass is the default user password Update the RTM alarm CPLD The procedures for updating the CPLD for the RTM are similar to the procedures in Update the legacy FPGA on page 58.
Board-level updates for the ATCA-45xx CPM and RTM 6 Updating the RTM SAS firmware The sasflash utility updates the LSI SAS firmware for the ATCA‐5400 and ATCA‐5401 RTM. The sasflash update file and two other files must be added to a USB flash drive to initiate the update. Follow these steps to update the LSI SAS on the RTM: 1. Contact Radisys Support to get the correct sasflash.efi update file for your RTM and CPM operating system. 2. Copy these files to a USB flash drive: • sasflash.
Board-level updates for the ATCA-45xx CPM and RTM 6 Compare the following example output with the information displayed on your adapter: ****************************************************************** LSI Corporation SAS FLASH Utility. SASFlash Version 1.20.00.00 (2008.10.31) Copyright (c) 2006‐2007 LSI Corporation. All rights reserved.
Board-level updates for the ATCA-45xx CPM and RTM 6 Using board level updates Manual CPM component downgrades are accomplished using the CPM update procedures in this chapter, beginning on page 46. Use the tools, scripts and utilities in the downgrade version of the CPM update bundle.
Chapter 7 Updating and customizing FRU data This chapter describes the procedures used to update or customize FRU data for a FRU or shelf. Radisys occasionally updates the functional aspects of FRU data, including PICMG point‐ to‐point connectivity records, with corrections or enhancements. The update procedures preserve the FRU‐specific information, such as the serial number. These procedures customize certain fields while preserving the functional aspects of the FRU data.
7 Updating and customizing FRU data Board Info Area: Board Product Name Board Part Number Board Custom 1 Board Custom 2 Board Custom 3 Product Info Area: Asset Tag Product Custom 1 Product Custom 2 Product Custom 3 2. From a Linux host, compile the custom fields .sf file into a .bin file: frugen.pl ‐f .sf ‐o .bin is the name of the file to be created. Make the base name match the base name. The script prompts to enter a value for each custom field. 3.
Updating and customizing FRU data 7 These fields can be uncommented: Chassis Info Area (for shelf FRU data only): #CHASSIS REPLACE CUSTOM 2 #CHASSIS REPLACE CUSTOM 3 #CHASSIS REPLACE CUSTOM 4 Board Info Area: #BOARD #BOARD #BOARD #BOARD #BOARD REPLACE REPLACE REPLACE REPLACE REPLACE PRODNAME PARTNUM CUSTOM 1 CUSTOM 2 CUSTOM 3 Product Info Area: #PRODUCT #PRODUCT #PRODUCT #PRODUCT REPLACE REPLACE REPLACE REPLACE ASSETAG CUSTOM 1 CUSTOM 2 CUSTOM 3 6.
Updating and customizing FRU data • 7 One of these pairs of files: • Files from Radisys with names ending in .cfg and .bin to use for upgrading the functional FRU information. Do not modify or compile these files before use. • Files with names ending in CustomFields.cfg and CustomFields.bin that are modified with custom data as described in Customizing FRU‐specific data on page 68. Note: The files ending in .sf are used for restoring corrupted FRU data only.
Chapter 8 Updating IPMI FW and FRU data for an AMC or RTM This chapter describes updating the AMC or RTM IPMI firmware using rsys‐ipmitool and updating the FRU data for an AMC or RTM using the rmcpta utility.
Updating IPMI FW and FRU data for an AMC or RTM 8 Updating the IPMI firmware The IPMI firmware for an RTM or AMC is updated using rsys‐ipmitool. Update the AMC or RTM IPMI firmware by following these steps: 1. Access the Linux or Windows command prompt. 2. Change directory to the location of the extracted AMC or RTM firmware images and tools. 3.
Updating IPMI FW and FRU data for an AMC or RTM 8 Reviewing the output The output from the IPMI firmware update commands should resemble the following example: PICMG HPM.1 Upgrade Agent 1.0: Validating firmware image integrity...OK Performing preparation stage... Services may be affected during upgrade.
Updating IPMI FW and FRU data for an AMC or RTM 8 Updating AMC or RTM FRU data The FRU data for an AMC or RTM must be updated using the rmcpta utility. Enter help on the rmcpta command line for a list of available commands. Update the AMC or RTM FRU data by entering the following commands: 1. rmcpta ‐h 2. targetfwd 3. updatefru backup.
Chapter 9 Installing previous firmware or software versions This chapter describes use of the firmware and tools comprised in an update bundle. Firmware is the image that is applied to the hardware, and tools are the update scripts that apply the firmware to the hardware. The latest version of tools should be used for upgrades and downgrades.
Installing previous firmware or software versions 9 Example rfw‐merge ATCA‐7220‐1.10.11‐1‐firmware.tgz ATCA‐7220‐1.11.13‐0‐firmware.tgz This command creates a new firmware bundle that contains older firmware with the latest versions of the update tools. Use this new bundle to downgrade the module. The new firmware bundle created by rfw‐merge is named using this format: ‐‐tools‐‐firmware.
Appendix A Sample conf.rfw file This appendix describes the conf.rfw configuration update file syntax, and lists some sample files that can be used as guidelines for creating the configuration file. Configuration file syntax The rfw‐update configuration files conform to the YAML file format. See http://search.cpan.org/dist/YAML/lib/YAML.pm for details, or run man YAML on the module where YAML is installed.
A Sample conf.rfw file update‐targets: module: connect: Required section listing the intended update targets. The required keys are: of the module type, which is used to verify the target. to connect to the module, where is: telnet://:@[:/] Note: You must have root account access for rfw‐update to operate properly.
A Sample conf.rfw file Specifies an alternative update bundle location for this target using the same syntax as the required key bundles:path. phase: <0‐999> Specifies a phase group. See Set up phase groups on page 22. post‐update: Specifies a post‐update script to run after the update is run and the module is rebooted to the updated bank. set‐bank: <0‐1> Forces the module to reboot to the specified boot bank before starting the update.
A Sample conf.rfw file This example shows how to format the file, with the “^” character representing the addition of a space: bundles: ‐ ^^^^module: ATCA‐1200 ^^^^path: tftp://192.168.16.1/ATCA‐1200‐1.10.20‐0‐firmware.tgz update‐targets: ‐ ^^^^connect: telnet://root@10.2.12.1 ^^^^module: ATCA‐1200 If conf.rfw is incorrectly formatted, the following error occurs: root@localhost@1‐2‐1:~# rfw‐update xbad ‐‐a ************************************** ** Tool version: rfw‐update‐2.0.
A Sample conf.rfw file Small sample conf.rfw file Below is a sample conf.rfw file for updating a lightly populated chassis. A more comprehensive conf.rfw file is provided at Full sample conf.rfw file on page 83 to copy and edit for creating a custom file. Formatting guidelines for conf.rfw on page 80 need to be followed when editing the copied file. Notice that there are two sections in the file—bundles and update‐targets.
A Sample conf.rfw file Full sample conf.rfw file The configuration file sample shown below can be copied into a text file, edited as necessary, and saved as conf.rfw. If this sample is copied, ensure that rfw‐update correctly processes the file by following the Formatting guidelines for conf.rfw on page 80. This full conf.rfw sample contains a more comprehensive set of module types and keys than the small sample, simplifying the editing process by providing a complete file framework.
A Sample conf.rfw file slot: phase: 10 1 connect: module: slot: phase: telnet://root:root@10.2.12.14 ATCA‐4500 14 1 connect: module: slot: phase: telnet://root:root@10.2.12.12 ATCA‐7220 12 1 connect: module: slot: set‐bank: telnet://root@10.2.12.8 ATCA‐2210 8 1 connect: module: slot: set‐bank: telnet://root@10.2.12.7 ATCA‐2210 7 0 connect: module: slot: ipmb‐target: telnet://root@10.2.12.8 ATCA‐5010 8 e6 connect: module: slot: ipmb‐target: telnet://root@10.2.12.
Appendix B IPMB and IPMB-L address mapping This appendix supplements Chapter 8, Updating IPMI FW and FRU data for an AMC or RTM, on page 72. Table 6 on page 86 provides the IPMB addresses of ATCA front modules, Power Entry Modules (PEMs), fan modules, and Shelf Peripheral Modules (SPMs) in Radisys ATCA shelves. The hexadecimal addresses in these tables may not be correct for shelves made by other manufacturers.
B IPMB and IPMB-L address mapping Table 6.
B IPMB and IPMB-L address mapping Table 7 provides the local IPMB addresses (IPMB‐L) for AMC and RTM devices, which is the IPMB from the carrier manager to the module. Each AMC and RTM connects to IPMB‐L through a module management controller (MMC). The hexadecimal addresses in this table may not be correct for shelves made by other manufacturers. If you are using a third‐party shelf, refer to the shelf's documentation for its IPMB‐L addresses. To comply with the AMC.
Appendix C Power cycling after IPMC FPGA upgrades Some Radisys products require a 48 V power cycle to activate new IPMC FPGA programming if the IPMC FPGA is updated. A 48 V power cycle is accomplished using one of these methods: • Removing the module from the shelf and then reinserting it • Removing and reapplying 48 V to the entire shelf The need to perform the power cycle depends on a variety of conditions, which are described in this appendix.
