IBM HMC on Power Firmware
Applies to: 7063-CR1
This document provides information about the installation of Licensed Machine or Licensed Internal Code, which is sometimes referred to generically as microcode or firmware.
1.3 Fix level Information on IBM Power HMC Components and Operating systems |
9.0 Quick Start Guide for Re- installing the HMC Image on the 7063-CR1 system |
This package provides firmware for IBM HMC on Power 7063-CR1 with minimum HMC version level of V8R870.0 only.
The firmware level in this package is:
•V3.07 with SMC BMC V3.08
There are the following images:
.pnor (Power firmware image)
.bin (BMC image)
pUpdate (tool binary)
Details on the package binaries are included in section 3.1.
Note 1: Before proceeding with an update to this service pack level, update the OS to the latest fix level for its release as there is an important fix for the AST driver that, if not applied, could prevent the system from IPLing after the service pack is installed.
Note 2: When upgrading firmware from firmware version 1.xx or 2.xx to version 3.xx:, there are dependencies between BMC and PNOR. For that reason, you must update BOTH BMC and PNOR while system power is off.
1. Power off the system
2. Update BMC version 3.xx using pUpdate 2.20
3. Wait for BMC to come back on line
4. Update PNOR version 3.xx using pUpdate 2.20
5. Power on the system to petitboot menu or OS.
6. When the system IPL reaches petitboot, SBE validation will be started automatically. This will take about 2 minutes. Please allow the system to complete the SBE validation before attempting to shutdown. If SBE validation fails for any reason, the system power will be turned off by firmware. Follow repair action given in the SEL to correct the problem.
7. Once the system reaches to OS, the system is ready to be used.
Downgrade of firmware from version 3.xx or later to version 2.xx or 1.xx is NOT supported.
This section specifies the "Minimum ipmitool Code Level" required by the System Firmware to perform firmware installations and managing the system. Open Power requires ipmitool level v1.8.15 to execute correctly on the V1.00 or later firmware.
Verify your ipmitool level on your linux workstation using the following commands:
bash-4.1$ ipmitool -V
ipmitool version 1.8.15
If you need to update or add impitool to your Linux workstation , you can compile ipmitool (current level 1.8.15) for Linux as follows from the Sourceforge:
1.1.1 Download impitool tar from http://sourceforge.net/projects/ipmitool/ to your linux system
1.1.2 Extract tarball on linux system
1.1.3 cd to top-level directory
1.1.4./configure
1.1.5 make
1.1.6 ipmitool will be under src/ipmitool
You may also get the ipmitool package directly from your workstation linux packages such as Ubuntu 14.04.3:
sudo apt-get install ipmitool
The BMC Web GUI is a web-based application that works within a browser. Supported browser levels are shown below with Chrome being the preferred browser:
•Google Chrome Version 46.0.2490.71 m
•Mozilla Firefox version 41.0.3
For specific fix level information on key components of IBM HMC model 7063-CR1 and the HMC software, please refer to the documentation in the IBM Knowledge Center.
https://www.ibm.com/support/knowledgecenter/8247-21L/p8eav/p8eav_7063_kickoff.htm
https://www.ibm.com/support/knowledgecenter/POWER8/p8had/p8had_hmc7063cr1.htm
Downgrading firmware from any given release level to an earlier release level is not recommended.
If you feel that it is necessary to downgrade the firmware on your system to an earlier release level, please contact your next level of support.
Concurrent Firmware Updates not available for the Power HMC.
Concurrent system firmware update is not supported on the Power HMC 7063-CR1.
The Petitboot user interface is started early in the boot process. When you are presented with the Petiboot user interface, it will take up to an additional 30 seconds for the user interface to be populated with boot options as storage and network hardware are being initialized. During this time, Petitboot will show the status message "Info: Waiting for device discovery". When Petitboot device discovery is completed, the following status message will be shown "Info: Connected to pb-discover!".
Use the following information to determine whether your installation will be concurrent or disruptive.
For the HMC 7063-CR1, the installation of system firmware is always disruptive.
The xxx.pnor file updates the primary side of the PNOR. The yyy.bin updates the primary side of the BMC only. The golden sides are unchanged.
Filename | Size | Checksum |
P8DTU20190513_IBM_7063CR1_sign.pnor | 33554560 | df4e68a982115adf8b3e3d04081a4a86 |
SMT_P8_308.bin | 33554432 | 95c5c5f09d1bee952fbe1d2cfdb0aa55 |
pUpdate_220_ppcle | 133824 | 00afbdb0690fa576019331bfab93e743 |
Note: The Checksum can be found by running the Linux/Unix/AIX md5sum command against the file (all 32 characters of the checksum are listed), ie: md5sum xxx.pnor.
After a successful update to the firmware level V2.10 , the PNOR components and BMC should be at the following levels. The ipmitool "fru" command can be used to display FRU ID 47 and the ipmitool "mc info" command can be used to display the BMC level.
Note: FRU information for the PNOR level does not show the updated levels via the fru command until the system has been booted once at the updated level.
PNOR firmware levels from FRU ID 47 inventory list for driver:
FRU Device Description : System Firmware (ID 47)
$ ipmitool -I lanplus -H xxx -U yyy -P zzz fru print 47
Product Name : OpenPOWER Firmware
Product Version : open-power-IBM-P8DTU-7063CR1-20190513-prod
Product Extra : op-build-fd96cc4
Product Extra : buildroot-2019.02.1-16-ge01dcd0
Product Extra : skiboot-v6.3.1
Product Extra : hostboot-p8-dc218d9-p4e07861
Product Extra : occ-p8-a2856b7
Product Extra : linux-5.0.7-openpower1-pe766c39
Product Extra : petitboot-v1.10.3
Product Extra : machine-xml-a44ee3e
BMC Level:
Display BMC firmware level using the "ipmitool mc info | grep Firmware" command:
Firmware Revision: 03.08
OP825 | |
V3.07 with SMC BMC V3.08 (OP825.30)
06/13/2019
| Impact: Security Severity: SPE
New features and functions
Support was added for a Self-Boot Engine (SBE) validation during the IPL to verify that the firmware images are the shipped versions.
Added BMC support to be able to detect Self Boot Engine (SBE) SEEPROM corruption
Added BMC support for new PNOR version partition that has a 4k signed header.
Security was enhanced for stunnel by allowing SSL Medium Strength and Anonymous Cipher Suites to be disabled. A reset of the stunnel configuration is required to do the disable using the following ipmitool commands one time: 1) ipmitool ... raw 0x30 0x70 0xB9 2) ipmitool ... mc reset cold
Added support in the SNMP client to allow connections to V2 and V3 servers to be running at the same.
Support was added for the BMC web gui to be able to enable and disable IPMI over LAN.
Added support for Active Directory to allow the BMC to make connections to LDAP\AD servers.
The BMC web gui was enhanced to display the IP address of the BMC.
For the IPMI DCMI configuration, the DCMI Discovery Configuratiuon (Option 12) is now enabled by default.
Sensor polling was enhanced to continue to work even after On-Chip Controller (OCC) goes into an error state.
Support for VUART/MBOX/FSI was enabled.
The BMC web gui was enhanced to be able to change the community string for the SNMP PET trap.
Support was added for a new BMC gui page to control the power capping of the system.
The BMC web gui was enhanced to show the PNOR version and build date. If the PNOR version is not found, only the PNOR build date is shown.
Support for tftp was added for BMC brick recovery (the old method of recovery has been deprecated).
Support has been removed from XIVE interrupt controller for the store EOI operation. Hardware has limitations which would require a sync after each store EOI to make sure the MMIO operations that change the ESB state are ordered. This would be performance prohibitive and the PCI Host Bridges (PHBs) do not support the synchronization.
Support was added to recognize a port parameter in the URL path for the Preboot eXecution Environment (PXE) in the ethernet adapters. Without the fix, there could be PXE discovery failures if a port was specified in the URL for the PXE.
System firmware changes that affect all systems
A security problem was fixed to prevent host programs from being able to corrupt the BMC using the internal software bridges between the host and BMC. The Common Vulnerabilities and Exposures issue number is CVE-2019-6260.
A security problem was fixed to detect and prevent Self Boot Engine (SBE) SEEPROM corruption. The Common Vulnerabilities and Exposures issue number is CVE-2018-8931.
A security problem was fixed to prevent a firmware update causing an unsigned image to be activated. The Common Vulnerabilities and Exposures issue number is CVE-2018-13787.
A security problem was fixed for the BMC ethernet Network Interface Card (NIC) device driver. The ethernet packet frames were not being padded with null bytes, which can allow remote attackers to obtain information from previous packets or kernel memory by using malformed packets, This fix protects against the Common Vulnerabilities and Exposures issue number CVE-2003-0001.
A problem was fixed for system hangs for early fails that occur in Hostboot. With the fix, the early fails are handled and recovery attempted to allow the IPL to succeed.
A problem was fixed for CGI aborts when uploading configurations using HTTP.
A problem was fixed for SSL certificate checks that were incorrectly failing on the check of the private key.
A problem was fixed for BMC remote console not conforming to security standards by not being digitally signed. The function has been updated to be cryptographically signed.
A problem was fixed for the host console losing data.
A problem was fixed for slow SOL console response for long-running commands.
A problem was fixed for an intermittent failure to IPL.
A problem was fixed for an intermittent system hang during IPL with "Power Status Error" in the SEL.
A problem was fixed for the BMC not showing all the sensor readings (except for OCC Active sensors which are always present) after an IPL.
A problem was fixed for an incorrect power cap setting when BMC sometimes incorrectly did not use the power cap setting from the host On-Chip Controller (OCC).
A problem was fixed for a failed SBE side not triggering a retry boot from the other SBE side.
A problem was fixed for an overrun of serial data from the host side to the BMC that caused loss of output character on the IPMI SOL console.
A problem was fixed for a "mc reset cold" being allowed during a IPL, causing a reboot of the BMC and an IPL failure. With the fix, the BMC cold reset is not allowed during the system IPL.
A problem was fixed for the BMC gui not being able to show all the System Event Log entries . "BMC gui -> Maintenance -> System Event Log " failed to display entire log with no scroll bar present to see new log entries.
A problem was fixed for pUpdate having troubles recovering from retry attempts and not be able to complete the firmware updates in a timely manner.
A problem was fixed for a IPv4 address change not persisting after a BMC reboot . This error can occur if the last octet of the IP address is reduced in characters by the IP address change. For the case where this was observed, the IP address was changed fro 50.6.36.100 to 50.6.36.1. But after the BMC reboot, the IP address again had two trailing zeros on IP as the IP address had reverted to 50.6.36.100.
A problem was fixed for an abnormal Java SOL display in Petitboot.
A problem was fixed for a missing failed operation description in the Session Audit SEL.
A problem was fixed in the BMC weg gui for logical volume color status.
A problem was fixed in the BMC web gui for not being able to mount an iso volume.
A problem was fixed for a BMC web gui freeze condition when an error event occurs on the backplane.
A problem was fixed for a "LanDrvinit fails to initial" message that was logging during the boot. There was no error in the boot as a wrong status value was returned to cause the message.
A problem was fixed for the power capping range allowed for the user. OCC provides two limits for minimum powercap. One being hard powercap minimum which is guaranteed by OCC and the other one is a soft powercap minimum which is lesser than hard-min and may or may not be asserted due to various power-thermal reasons. So to allow the users to access the entire powercap range, this fix exports soft powercap minimum as the “powercap-min” DT property. And it also adds a new DT property called “powercap-hard-min” to export the hard-min powercap limit.
A problem was fixed for lost output on the console when the OS is stopping or rebooting. With the fix, the console output is always flushed before stopping the system.
A problem was fixed for the AST VGA device which could sometimes fail to initialize when the vendor ID for the device was parsed incorrectly.
A problem was fixed for a system hang that could occur while printing with system debug options and having a active user on the console.
A problem was fixed for an intermittent opal-prd crash that can happen on the host OS. This is the fault signature: " opal-prd[2864]: unhandled signal 11 at 0000000000029320 nip 00000 00102012830 lr 0000000102016890 code 1"
A problem was fixed for diagnostic code trying to read sensor values for PCI Host Bridge (PHB) entries that are unused, which causes debug output to have incorrect values for the unused entries. With the fix, only the used entries are processed by the diagnostic code.
A problem was fixed for Petitboot exiting to the shell with xCAT genesis in the menu when trying to do a network boot. Petitboot was timing out when trying to access the ftpserver but it was not doing the network re-queries necessary for a proper retry. If this error happens on a system, it can be made to boot with the following two steps: 1) Type the word "exit" and press enter key. This brings it back to petitboot menu. 2) Press the enter key again to start the boot of the xCAT image.
A problem has been fixed for a slow start up of a process that can occur when the system had been previously in an idle state.
A problem has been fixed for a TOD error that can cause a soft lockup of the kernel. A 'soft lockup' is defined as a bug that causes the kernel to loop in kernel mode for more than 20 seconds, without giving other tasks a chance to run. The current stack trace is displayed upon detection and, by default, the system will stay locked up.
A problem has been fixed to add part and serial numbers to the processors when accessed through the device tree.
A problem has been fixed to make the OS aware of the DARN random number generator at 0x00200000 PPC_FEATURE2_DARN) and the SCV syscall at 0x00100000 (PPC_FEATURE2_SCV). Without this fix, these service constants are not defined in the OS userspace.
A problem was fixed for Coherent Accelerator Processor Proxy (CAPP) mode for the PCI Host Bridge (PHB) to improve DMA write performance by enabling channel tag streaming for the PHB. With this enabled, the DMA write does not have to wait for a response before sending a new write command on the bus.
A problem was fixed for the Open-Power Flash tool "pflash" failing with a blocklevel_smart_erase error during a pflash. This problem is infrequent and is triggered if pflash detects a smart erase fits entirely within one erase block.
A problem was fixed in the Petitboot user interface to handle cursor mode arrow keys for the VT100 'application' cursor to prevent mis-interpreting an arrow key as an escape key in some situations. For more information on the VT100 cursor keys, see http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO-21.html.
A problem was fixed in the Petitboot user interface to cancel the autoboot if the user has exited the Petitboot user interface. This prevents the user dropping to the shell and then having the machine boot on them instead of waiting until the user is ready for the boot.
A problem was fixed in the Petitboot parsing of manually-specified configuration files that caused the parser to create file paths relative to the downloaded file's path, not the original remote path.
A problem was fixed for a flood of OPAL error messages that can occur for a processor fault. The message "CPU ATTEMPT TO RE-ENTER FIRMWARE" appears as a large group of messages and precede the relevant error messages for the processor fault. A reboot of the system is needed to recover from this error.
A problem was fixed for a skiboot hang that could occur rarely for a i2C request if the i2c bus is in error or locked by the On-Chip Controller (OCC).
A problem was fixed for an OS reboot after a shutdown that intermittently fails after the shutdown. This can happen if the BMC is not ready to receive commands. With the fix, the messages to the BMC are validated and retried as needed. To recover from this error, the system can be rebooted from the BMC interface.
A problem was fixed for a kernel hard lock up that could occur if IPMI synchronous messages were sent from the OS to BMC while the BMC was rebooting. For these type of messages, a processor thread remains waiting in OPAL until a response is returned from the BMC. |
V2.30 (OP825.21)
03/12/2018
| Impact: Security Severity: SPE
Response for Recent Security Vulnerabilities
In response to recently reported security vulnerabilities, this firmware update is being released to address Common Vulnerabilities and Exposures issue numbers CVE-2017-5715, CVE-2017-5753 and CVE-2017-5754.
New features and functions
Support was added for the user to be able to create a BMC group name via LDAP. This provides a BMC login privilege by group name.
Support was added for a new alert message that occurs on the BMC web gui when a disk, power supply, or a fan is unplugged. When an event is logged against one of the associated sensors, the alert message is sent.
Support for a 2 MB IPMI SOL console data capture and download.
Support for "Product Extra Information" for FRU reading on the BMC GUI web.
System firmware changes that affect all systems
A problem was fixed for RHEL7.3 GUI mode having a large square cursor via the BMC iKVM console. This oversized cursor can interfere with normal operations on the screen by blocking the view of task options on pull-down menus.
A problem was fixed for a duplicate sensor id for occ_active and boot_count which shared a device id of "0x09". This caused one of the sensors to be absent from the sensor device tree and also caused an OPAL error log: "[ 84.176082494,3] DT: dt_attach_root failed, duplicate sensor@9". There was no other adverse impact for this problem other than the missing sensor information. With the fix, the boot count sensor has a new device code of "0x0A".
A problem was fixed for an IPMI SOL Console drop during a PNOR firmware update. There is a log message "SOL session closed by BMC", but there is no impact on the system.
A problem was fixed for an IPMI DCMI "Get Power Reading" command average reading being inaccurate.
A problem was fixed for the FRU information for MfgDatetime which was not displayed correctly.
A problem was fixed for "SENSOR_ID" not being consistent with the sensor name in email alerts.
A problem was fixed for opening the Java iKVM program on a Mac OS X client system.
A problem was fixed in the BMC NTP support to protect against a possible denial-of-service attack in the NTP processing of a query. This is for protection against the Common Vulnerabilities and Exposures (CVE) number CVE-2016-7434.
A problem was fixed for an erroneous voltage reading at an empty CPU socket.
A problem was fixed for iKVM not showing the Hostboot and OPAL boot progress.
A problem was fixed for the BMC not requesting an OCC reset if the OCC is in Safe mode but the "OCC Active" sensor is still enabled. With the fix, after sixty seconds of the OCC being in Safe mode, the OCC reset will be requested regardless of the state of the "OCC Active" sensor.
A problem was fixed for the On-Chip Controller (OCC) dropping to Safe mode during BMC communication failures when an OCC reset was requested.
A problem was fixed for the OpenPOWER logo being pixelated (a very low-resolution image) in the Java iKVM viewer.
A problem was fixed for a SMASH console hang from the BMC SSH login: Start the SMASH console by typing "start /system1/sol1". Note that the command is unresponsive, and does not show a login prompt. With the fix, this sequence is responsive and shows the same console as the IPMI SOL console.
|
V2.20
10/13/2017 | Impact: New Severity: New System firmware changes that affect all systems
A problem was fixed for an unattended boot hang that can occur during an HMC upgrade. This problem may be circumvented by the user intervening and selecting ‘Rescan Device’, then both menu entries will be shown correctly and the boot can continue. A problem was fixed for intermittent warm reboot failures because of invalid memory references. The problem may be circumvented by attempting the reboot again or power cycling and booting again.
|
V2.10 | Impact: New Severity: New New features and functions for 7063-CR1: GA Level
Support the HMC appliance with 4x8GB memory configuration by allowing system to IPL with partial failure of memory DIMMs.
Support for resonant clocking was enabled to reduce power consumption of the processors for an approximate 10W per processor socket savings.
The Preboot Execution Environment (PXE) installation process was enhanced to provide more status log information and to show percentage-based download progress information.
Support was added for an On-Chip Controller (OCC) Soft User Power Cap. Previously, if the User Power Cap was being exceeded and could not be maintained, the OCC placed the system into Safe mode (a power mode with reduced processor frequencies).. With the Soft User Power Cap feature, the Safe mode is not used when the User Power Cap is exceeded. Instead, the OCC will log an error and continue to try to maintain the User Power Cap.
System firmware changes that affect all systems
A problem was fixed for a missing device discovery message and overly verbose output messages during the boot. It is now less verbose during the boot-only error-level messages are printed during Petitboot bootloader initialization. This means that there will be fewer messages printed as the system boots. Additionally, the Petitboot user interface is started earlier in the boot process. This means that the user will be presented with the user interface sooner, but it may still take time, potentially up to 30 seconds, for the user interface to be populated with boot options as storage and network hardware is being initialized. During this time, Petitboot will show the status message "Info: Waiting for device discovery". When Petitboot device discovery is completed, the following status message will be shown "Info: Connected to pb-discover!".
System firmware changes that affect certain systems
On systems with maximum memory configurations (where every DIMM slot is populated; size of DIMM does not matter), a problem has been fixed for systems losing performance and going into Safe mode (a power mode with reduced processor frequencies intended to protect the system from over-heating and excessive power consumption). This happened because of On-Chip Controller (OCC) time out errors when collecting Analog Power Subsystem Sweep (APSS) data, used by the OCC to tune the processor frequency. This problem occurs more frequently on systems that are running heavy workloads. Recovery from Safe mode back to normal performance can be done with a reboot of the system.
|
OS levels supported by the 7063-CR1 servers:
- HMC V9 R1 M910 or later
The HMC stack runs on an embedded Linux distribution. The HMC on Power version V9 R1 M910 or later is supported on the 7063-CR1.
Notice: Only Enhanced HMC GUI is supported (no classic GUI) on HMC V8R870.0 and later.
The below link is to a guide on how to use the HMC to perform management and partition tasks for IBM Power servers:
https://www.ibm.com/support/knowledgecenter/POWER8/p8hdx/p8_workingwithconsoles_op.htm
Use the following steps in the below link to navigate the HMC GUI to determine the HMC level:
https://www.ibm.com/support/knowledgecenter/8247-21L/p8hai/p8hai_viewcodelevel_enh.htm
Use the ipmtool "fru" command or the BMC Web GUI FRU option to look at product details of FRU 47.
ipmitool -I lanplus -H <bmc host IP address> -P admin -U ADMIN fru print 47
Follow the instructions on Fix Central. You must read and agree to the license agreement to obtain the firmware packages.
Note 1: Before proceeding with an update to this service pack level, update the OS to the latest fix level for its release as there is an important fix for the AST driver that, if not applied, could prevent the system from IPLing after the service pack is installed.
Note 2: When upgrading firmware from firmware version 1.xx or 2.xx to version 3.xx, there are dependencies between BMC and PNOR. For that reason, you must update BOTH BMC and PNOR while system power is off.
1. Power off the system
2. Update BMC version 3.xx using pUpdate 2.20
3. Wait for BMC to come back on line
4. Update PNOR version 3.xx using pUpdate 2.20
5. Power on the system to petitboot menu or OS.
6. When the system IPL reaches petitboot, SBE validation will be started automatically. This will take about 2 minutes. Please allow the system to complete the SBE validation before attempting to shutdown. If SBE validation fails for any reason, the system power will be turned off by firmware. Follow repair action given in the SEL to correct the problem.
7. Once the system reaches to OS, the system is ready to be used.
Downgrade of firmware from version 3.xx or later to version 2.xx or 1.xx is NOT supported.
The updating and upgrading of system firmware depends on several factors, such as the current firmware that is installed, and what operating systems is running on the system.
These scenarios and the associated installation instructions are comprehensively outlined in the firmware section of Fix Central, found at the following website:
http://www.ibm.com/support/fixcentral/
Any hardware failures should be resolved before proceeding with the firmware updates to help insure the system will not be running degraded after the updates.
The pUpdate utility is provided with the firmware update files from IBM Fix Central. It can be used to perform out-of-band updates by selecting the "-i lan" parameter on the command invocation. The code update needs to be done in two steps: 1) Update the BMC firmware and 2) Update the CEC PNOR for the hostboot and the OPAL components. It is recommended that the BMC be updated first unless otherwise specified in the firmware install instructions.
If a network connection can be made to the BMC, an out-of-band update can be done with the following LAN invocation from a Linux companion system:
BMC update: " pUpdate -f bmc.bin -i lan -h xx.xx.xx.xx -u ADMIN -p ADMIN -r y" where bmc.bin is the name and location of the BMC image file, xx.xx.xx.xx is the IP address of the BMC.
PNOR update: "pUpdate -pnor pnor.bin -i lan -h xx.xx.xx.xx -u ADMIN -p ADMIN " where pnor.bin is the name and location of the PNOR image file and xx.xx.xx.xx is the IP address of the BMC.
For more details on how to use the pUpdate utility, refer to the following link:
https://www.ibm.com/support/knowledgecenter/POWER8/p8eit/p8eit_update_firmware_pupdate.htm
You can use diagnostic utilities to diagnose adapter problems.
For more details on how to use the diagnostic utilities, refer to the following link:
https://www.ibm.com/support/knowledgecenter/POWER8/p8eit/p8eit_diags_kickoff.htm
Another method to update the system firmware is by using the baseboard management controller (BMC).
The system firmware is a combination of the BMC firmware and the PNOR firmware. To update the system firmware, update both the BMC firmware and the PNOR firmware by using the BMC.
Note: System firmware update from the BMC Web GUI is only supported on Google Chrome and Mozilla Firefox browsers.
Complete the following steps to update the BMC firmware:
1. Log in to the BMC by entering the user name and password. Then, press Enter.
2. From the Maintenance list on the BMC dashboard, select Firmware Update.
3. In the Firmware Update window, select Enter Update Mode. Click OK.
4. In the Firmware Upload window, choose the .bin file from your local system folder and click Upload Firmware. Wait for the file to be uploaded. Then, click OK.
5. The existing and new versions of the BMC firmware are displayed. Ensure that the Preserve Configuration check box is selected and the Preserve SDR check box is not selected. Click Start Upgrade.
Note: You cannot perform other activities by using the BMC interface until the firmware update is complete.
6. The upgrade progress of the firmware update is displayed. After the firmware update is complete, the system is restarted.
7. After the restart of the system is complete, verify the firmware revision level in the System menu of the BMC dashboard.
Complete the following steps to update the PNOR firmware:
1. Log in to the BMC by entering the user name and password. Then, press Enter.
2. From the Maintenance list on the dashboard, select PNOR Update.
3. In the PNOR Upload window, choose the .pnor file from your local system folder and click Upload PNOR. Wait for the file to be uploaded. Then, click OK.
4. The existing and new dates of the PNOR firmware are displayed. Click Start Upgrade.
Note: You cannot perform other activities by using the BMC interface until the PNOR update is complete.
5. The progress of the PNOR update is displayed. After the PNOR update is completed, the system must be restarted to finish installation of the new PNOR firmware.
For more information on updating the firmware using the BMC, refer to the following link:
https://www.ibm.com/support/knowledgecenter/POWER8/p8eit/p8eit_update_firmware_bmc.htm
The service processor, or baseboard management controller (BMC), provides a hypervisor and operating system-independent layer that uses the robust error detection and self-healing functions that are built into the POWER8 processor and memory buffer modules. Open power application layer (OPAL) is the system firmware in the stack of POWER8 processor-based Linux-only servers.
The service processor, or baseboard management controller (BMC), is the primary control for autonomous sensor monitoring and event logging features on the Power HMC.
The BMC supports the Intelligent Platform Management Interface (IPMI) for system monitoring and management. The BMC monitors the operation of the firmware during the boot process and also monitors the OPAL hypervisor for termination. The firmware code update is supported through the BMC and Intelligent Platform Monitoring Interface (IPMI) and the BMC Web GUI The GUI console is accessed using a web browser with a "http:" connection to port. See section 1.2 for the supported browsers that can be used with BMC Web GUI.
The Open Power Abstraction Layer (OPAL) provides hardware abstraction and run time services to the running host Operating System.
For the 7063-CR1 servers, only the OPAL bare-metal installs of the Hardware Management Console are supported.
Find out more about OPAL skiboot here:
https://github.com/open-power/skiboot
The Intelligent Platform Management Interface (IPMI) is an open standard for monitoring, logging, recovery, inventory, and control of hardware that is implemented independent of the main CPU, BIOS, and OS. The 7063-CR1 HMC provides one 10M/100M baseT IPMI port.
The ipmitool is a utility for managing and configuring devices that support IPMI. It provides a simple command-line interface to the service processor. You can install the ipmitool from the Linux distribution packages in your workstation, sourceforge.net, or another server (preferably on the same network as the installed server). For example, in Ubuntu, use this command:
$ sudo apt-get install ipmitool
For installing ipmitool from sourceforge, please see section 1.1 "Minimum ipmitool Code Level".
For more information about ipmitool, there are several good references for ipmitool commands:
1.The man page
2.The built-in command line help provides a list of IPMItool commands:
# ipmitool help
3.You can also get help for many specific IPMItool commands by adding the word help after the command:
# ipmitool channel help
4.For a list of common ipmitool commands and help on each, you may use the following link:
www.ibm.com/support/knowledgecenter/linuxonibm/liabp/liabpcommonipmi.htm
To connect to your host system with IPMI, you need to know the IP address of the server and have
a valid password. To power on the server with the ipmitool, follow these steps:
1. Open a terminal program.
2. Power on your server with the ipmitool:
ipmitool -I lanplus -H bmc_ip_address -P ipmi_password power on
3. Activate your IPMI console:
ipmitool -I lanplus -H bmc_ip_address -P ipmi_password sol activate
Petitboot is a kexec based bootloader used by IBM POWER8 systems for doing the bare-metal installs on the 8001 servers.
After the POWER8 system powers on, the petitboot bootloader scans local boot devices and network interfaces to find boot options that are available to the system. Petitboot returns a list of boot options that are available to the system. If you are using a static IP or if you did not provide boot arguments in your network boot server, you must provide the details to petitboot. You can configure petitboot to find your boot with the following instructions:
https://www.ibm.com/support/knowledgecenter/linuxonibm/liabp/liabppetitbootadvanced.htm
You can edit petitboot configuration options, change the amount of time before Petitboot automatically boots, etc. with these instructions:
https://www.ibm.com/support/knowledgecenter/linuxonibm/liabp/liabppetitbootconfig.htm
After you select to boot the ISO media for the Hardware Management Console, the installer wizard for that Linux distribution walks you through the steps to set up disk options, your root password, time zones, and so on.
You can read more about the petitboot bootloader program here:
https://www.kernel.org/pub/linux/kernel/people/geoff/petitboot/petitboot.html
This guide helps you re-install HMC on the 7063-CR1.
1.) Create the virtual drive on the 7063-CR1 system, if needed.
Follow the steps in this procedure in the unlikely event that you need to re-create the virtual drive on the IBM 7063-CR1 Hardware Management Console.
About this task
This procedure assumes that:
The system was erroneously shipped without an already created and pre-loaded virtual disk
The existing virtual disk is somehow damaged and needs to be re-created.
Link to procedure: https://www.ibm.com/support/knowledgecenter/en/8286-41A/p8ej8/p8ej8_recreate_drive.htm
2.) Use the HMC media to update or re-install the HMC. If the virtual disk had to be created in step 1, the HMC recovery media will be needed to re-install the HMC.
Follow the steps in the link below for upgrading the level of the HMC to obtain and install the recovery media:
https://www.ibm.com/support/knowledgecenter/TI0003M/p8hai/p8hai_upgrades_enh.htm
Date | Description |
09/18/2017 | New for HMC model 7063-CR1 for V2.10 release |
10/13/2017 | Service pack 1 release, version V2.20 |
03/12/2018 | Service pack release, version V2.30 (OP825.21) |
06/13/2019 | Service pack release, version V3.07 (OP825.30) |
07/08/2019 | Update sections 4.0/4.1 with newer minimum required HMC level requirements (there are no updates to the delivered binaries) |