IBM Power System Firmware Upgrade

Introduction:

IBM Power System firmware controls low-level hardware functions of the server frame (CEC – Central Electronics Complex). Keeping firmware up to date ensures:

• Hardware stability
• Security fixes
• Performance improvements
• Compatibility with new HMC levels
• Support for new adapters and features

Firmware updates are performed through the HMC and must follow IBM-supported upgrade paths and compatibility matrices.

There are two types of firmware updates:

• Concurrent Firmware Update
• Disruptive Firmware Update

Choosing the correct method is critical to avoid unexpected downtime.

IBM Frame Firmware Update Types:

Concurrent Firmware Update

Description:

Firmware is updated while the system remains powered on and operational.

When to Use

• Supported by current firmware level
• Supported by HMC version
• Minimal downtime is required
• Production workloads must remain online

Benefits

• No need to shut down LPARs
• No need to stop Virtual I/O Servers
• Minimal production impact

Limitations

• Not supported on all firmware levels
• Some updates may require later reboot
• Certain hardware adapters may block concurrent update

Disruptive Firmware Update:

Description:

System must be powered off or rebooted to complete the firmware update.

When Required

Current firmware level does not support concurrent update

Major firmware change

IBM release notes specify disruptive update only

Impact

All LPARs must be shut down

Virtual I/O Servers must be shut down

Full system downtime required

How to Decide Which Update Type to Use

Before starting:

Run HMC Readiness Check

HMC → Select System → Actions → Update Firmware → Check Readiness

If status shows Ready for Concurrent, you may use concurrent update.

If not, disruptive update is required.

Check IBM compatibility matrix:

https://www.ibm.com/support/pages/hmc-and-system-firmware-supported-combinations

Review release notes from IBM Fix Central.

Always prefer Concurrent when supported and safe.

Use Disruptive when required or recommended.

IBM Power System Firmware Upgrade Checklist

Step 1 — Pre-Check Compatibility

1.1 Verify HMC & Firmware Combination

Check IBM supported combinations page:

https://www.ibm.com/support/pages/hmc-and-system-firmware-supported-combinations

Example for model 9080-M9S:

https://www.ibm.com/support/pages/node/7080068

Confirm:

HMC level supported

Target firmware level supported

Adapter compatibility confirmed

1.2 Confirm Firmware Repository

Ensure firmware image is available locally or via NIM:

Example:

nimserver01:/software/firmware/9080-M9S

Step 2 — Run Firmware Readiness Check

On HMC:

Select target system

Navigate:

Actions → Update Firmware → Check Readiness

Confirm status = Ready

If not ready:

Review blocking issues

Resolve adapter or firmware mismatch

Step 3 — Prepare for Firmware Upgrade (Disruptive Case)

Skip shutdown steps if performing Concurrent Update.

For disruptive update:

• Stop Application
• Stop Database
• Shutdown all LPARs
• Shutdown Virtual I/O Servers (VIO A & B)

Verify all partitions are in Not Activated state.

Step 4 — Perform Firmware Upgrade

On HMC:

Select Target System

Navigate:

Actions → Update Firmware → Update Firmware

Choose:

System Firmware → Update

Select Update Type:

Concurrent (if supported)

Disruptive (if required)

Select firmware image source (local repository, NFS, etc.)

Confirm and start update

Monitor progress

Wait until system state returns to:

Operating

or

Standby

Step 5 — Post Firmware Upgrade Tasks

5.1 Start Virtual I/O Servers

Login to HMC (SSH or PuTTY):

chsysstate -m <Frame_Name> -r lpar -n <VIO-ServerA> -o on

chsysstate -m <Frame_Name> -r lpar -n <VIO-ServerB> -o on

Wait until both are fully operational.

5.2 Start Application LPARs

chsysstate -m <Frame_Name> -r lpar -n <LPAR-A> -o on

chsysstate -m <Frame_Name> -r lpar -n <LPAR-B> -o on

5.3 Validate System Health

Check Filesystems

# df -g

Validate PowerHA Cluster (if used)

# clRGinfo

Validate GPFS (if used)

# mmgetstate -a

Validate Services

# lssrc -s sendmail

5.4 Start Database & Applications

• Start Database
• Start Application services
• Confirm user access
• Validate monitoring alerts

Post-Upgrade Validation Checklist

• Firmware level verified on HMC
• System status = Operating
• VIO A & B running
• All LPARs running
• Cluster healthy (if applicable)
• Storage paths active
• No hardware errors
• Applications accessible

Best Practices

• Always review release notes before updating
• Prefer concurrent update when supported
• Test in non-production first
• Schedule maintenance window for disruptive updates
• Verify cluster and storage health after update
• Keep HMC level compatible with firmware