IBM Developer

Tutorial

Perform IBM Power firmware updates through the IBM i operating system in the manufacturing default configuration mode

A step-by-step guide to update eBMC firmware using IBM i OS

By Jyothi Prasanna Bhupathiraju, Thumati Sasibindu

The purpose of this tutorial is to guide users through the process of updating enterprise baseboard management controller (eBMC) firmware on IBM i systems configured in manufacturing default configuration mode, which is essential for maintaining system reliability, applying critical fixes, and ensuring compatibility with newer hardware and software features — especially in environments without the support of Hardware Management Console (HMC).

Understanding the manufacturing default configuration mode

Manufacturing default configuration refers to the initial single-partition setup of a managed system, as delivered by your service provider.

In the manufacturing default configuration mode:

  • You can operate the system as a non-partitioned server.
  • You can install an OS directly on the managed system.
  • You don’t need a Hardware Management Console (HMC) to manage the system.

This configuration is typically used during the initial setup or for standalone environments.

Prerequisite steps for IBM i OS in the manufacturing default configuration mode

Before initiating the firmware update process in the manufacturing default configuration mode, ensure the following system requirements and configurations are in place to avoid boot failures and compatibility issues:

  • Supported server models:

    IBM i supports the MDC mode only on scale-out servers. The supported models for IBM Power10 and IBM Power11 systems are as follows:

    • Power10 (supported on all active IBM i releases):

      • 9105-22B (2S2U-ioSCM): 1-core only (no Virtual Partition Manager support)
      • 9105-41B (1S4U-ioSCM)
      • 9105-42A (2S4U)
      • 9028-21B: 1-core feature does not support virtual hosting or Virtual Partition Manager
    • Power11 (supported on all active IBM i releases):

      • 9824-22A (2S2U: DCM or ioSCM): 2x4-core feature only
      • 9824-42A (2S4U-DCM)
  • Huge pages configuration

    IBM i does not support huge pages. Ensure that no huge pages are allocated on the server, as these are inherited by the partition in the MDC mode.

    This setting must be configured in the Advanced System Management Interface (ASMI).

    If huge pages are allocated, the partition boot fails with the system reference code (SRC) B2008105.

  • NVMe drive policy

    Remove the Non-Volatile Memory Express (NVMe) drive locking policy before proceeding with the MDC mode setup.

Load source configuration

Follow the step to re-tag the load source after configuring the manufacturing default configuration and switching to non-HMC-managed mode.

As shown in Figure 1, the user must specify the IBM i load source that will be used to boot the IBM i operating system.

Load source configuration Figure 1: Load source configuration

BMC tagging

This option only works when the server is running FW 1060 or its succeeding versions (BMC only). The following steps outline how to configure BMC settings in ASMI to enable IBM i partition boot in the manufacturing default configuration mode, ensuring the system is correctly tagged and ready for firmware updates:

  1. In the BMC ASMI, set the server in the power off mode and restart it by setting the Server firmware start policy set to Standby. Monitor the progress until the SRC changes to Standyby.
  2. On the Server power operations panel, set the Default partition environment to IBM i.
  3. Set the IBM i partition boot mode to B.
  4. Set the IBM i load source to the location code of the load source disk.
  5. Set the IBM i console to the location code of a live ethernet card.
  6. Do not set the IBM i alternate restart device before you set the boot mode to D (install).
  7. Click Save to save changes and continue with the running OS.

    The partition will boot in the manufacturing default configuration mode.

How to verify the manufacturing default configuration mode

Use the following steps to verify that your IBM i partition is operating in the manufacturing default configuration mode by leveraging service tools and diagnostic options.

Prerequisite

Boot the IBM i partition in Manual Mode from the ASMI. Once the OS is booted in Manual Mode, you will have access to the console.

Steps with details:

  1. Select Option 3 – Use Dedicated Service Tools

    Access IBM i service tools for advanced system management and diagnostics.

  2. Select Option 7 – Start a Service Tool

    Launches the service tool environment to run commands and perform system analysis.

  3. Select Option 1 – Display/Alter/Dump

    View or modify the system storage and internal code data. From the next page, choose one of the following options:

    • Option 1 – Display/Alter Storage: Allows you to view and modify storage-related attributes, including partition configuration.
    • Option 2 – Licensed Internal Code Data: Displays internal code data for troubleshooting and advanced analysis.
    • Option 14 – Advanced Analysis: Provides tools for running diagnostic commands and scripts.
  4. Run the command

    Enter 1 for Display/Alter Storage, then type:

    iopfr -partitionatr
    

    Purpose: This command retrieves partition attributes, including manufacturing default configuration mode and the HMC-managed mode status.

  5. Click Enter on the options screen.

    Result:

    • The console displays:

      • Manufacturing default configuration mode

      • HMC-Managed Mode Status

        (Value: 1 = True, meaning enabled)

Apply the PTF on IBM i OS

Once the IBM i partition has successfully booted in the manufacturing default configuration mode and its status is verified, the system is ready for firmware updates. The next step involves applying program temporary fixes (PTFs), which are essential for updating and maintaining the firmware. The following link will help you download and apply PTFs using IBM Fix Central.

Tool to access IBM i OS

IBM i uses the tool Access Client Solutions to access the OS, and it is a software suite that allows users to connect and manage IBM i Power Systems (formerly known as AS/400 or iSeries) from various operating systems like Windows, macOS, and Linux. It provides a range of tools for tasks such as 5250 terminal emulation, database management, file system navigation, system administration, and application development.

To perform firmware updates and system management tasks on IBM i OS in the manufacturing default configuration mode, access the operating system using IBM's Access Client Solutions.

The following steps outline how to launch and use Access Client Solutions to connect to the IBM i system console.

  1. As shown in Figure 2, the user is required to enter the System name and console details.

    IBM i Access Client Solutions Figure 2: IBM i Access Client Solutions

  2. Once the Access Client Solution is activated, it automatically launches the Remote 5250 Console interface.

  3. As shown in Figure 3, log into the prompt to access the OS.

    IBM i Access Client Solutions Figure 3: Console

  4. Enter the following details:

    • User: user_name
    • Password: password

    IBM i Access Client Solutions Figure 4: Sign On screen

  5. As shown in Figure 5, from the IBM i Main Menu screen, use the DSPFMWSTS command to verify whether the system is operating in the manufacturing default configuration mode or the HMC mode.

    IBM i Main Menu Figure 5: IBM i Main Menu

  6. As shown in Figure 6, the Firmware update policy is set to OPSYS, indicating that the system is operating in the manufacturing default configuration mode.

    Display Firmware Status screen Figure 6: Display Firmware Status screen

  7. Once the IBM i OS firmware status is set to the MDC mode, use sendPTF to send PTF images to the OS.

  8. After the Send Fix to System process is complete, the firmware status transitions to the Staged state, as shown in Figure 7.

    Display Firmware Status screen Figure 7: Display Firmware Status screen

  9. Reboot the operating system to initiate the firmware update process. Use the following command to reboot the system.

    PWRDWNSYS ( )
    

    BM i Main Menu screen Figure 8: IBM i Main Menu screen

  10. After rebooting the operating system, verify the updated firmware version.

    System information** screen Figure 9: System information screen

    Refer to Figure 9 to identify the most recent version of the System Information screen.

    The firmware update is successfully completed on the IBM i OS, which is verified by the update status as shown in Figure 10.

    System information** screen Figure 10: Display Firmware Status screen

Conclusion

This tutorial explained the steps to update the firmware on eBMC via IBM i OS in the Manufacturing Default Configuration mode. By leveraging tools like sendPTF and Access Client Solutions, administrators can efficiently manage firmware updates directly from the IBM i OS without relying on an HMC. Following the steps explained in the tutorial ensures a smooth and reliable update process, helping maintain system integrity and performance in standalone environments.

SendPTF Ref:

IBM Fix Central