BL920s-2015.12b-ReleaseNotes.htm

TITLE: HPE Integrity Superdome X Servers Firmware Bundle – for HP SUM Smart Update Manager

VERSION:
Bundle version: 2015.12
Firmware version: 7.6.0

HP Smart Update Manager (HP SUM)
HP SUM Version: 7.3.0

DESCRIPTION:
This bundle contains the HP Smart Update Manager (HP SUM) x86 application with the complex and nPartition firmware for the HPE Integrity Superdome X Server with Gen8 and Gen9 blades. It includes an integrated OA (Onboard Administrator). This bundle can be used to update the firmware through the OA using the HP SUM application.

WARNING: If you are updating from a version prior to 6.0.42, you must install 6.0.42 (bridge release for digital signing) prior to updating to version 7.5.0 or later.

Note:

Superdome X firmware includes two distinct parts, the Complex firmware (for primary server management), and the Partition firmware (code that runs on blade system processors).
Firmware version 7.5.0 or later is required to support BL920s Gen9 blades.
Superdome X version 5.73.0 or later supports online complex firmware update:

The update of the Complex firmware takes effect without any additional operator interaction; some server management capabilities will become inactive until the update completes.
The new Partition firmware however only gets programmed into the Flash ROM during the update, and a partition reboot is required to activate it. This enables rolling upgrades, where the new Partition firmware may get activated on one partition at a time, when it is convenient to bring the partition down for a reboot.

This “mixed” operational mode is supported for an indefinite period of time, provided the combinations of Complex and Partition firmware are compatible. The table below describes those supported compatible Complex/Partition firmware combinations:

“Yes” in the cell means that the combination for the Partition (row)/ Complex (column) is supported and “No” that it is not supported.
Note:

The complex firmware version must always be greater than or equal to the partition firmware (but not all such combinations are supported).
Online firmware downgrade is not supported.

		Complex Firmware
		5.50.12¹	5.73.0¹	6.0.42	7.5.0	7.6.0
Partition Firmware	5.50.12	Yes	No	No	No	No
	5.73.0	No	Yes	Yes	Yes^1,3	Yes^1,3
	6.0.42	No	No	Yes	Yes^2,3	Yes^2,3
	7.5.0	No	No	No	Yes	Yes
	7.6.0	No	No	No	No	Yes

Note 1: Updating Complex FW from 5.X.X to 7.5.0 or later requires installing 6.0.42 first because of changes to the digital firmware bundle signature.

Note 2: Online Complex FW updates from 6.0.42 to 7.5.0 or later will show “Mixed” firmware due to newer PDH FPGA in 7.5.0. Partition operation is supported in this condition. To complete the PDH FPGA update, turn off the partition(s) when convenient, and rerun firmware update.

Note 3: BL920s Gen8 Blades support running Complex FW version 7.5.0 or later with Partition FW 5.73.0 or 6.0.42, but Gen9 Blades require both Complex and nPartition FW version 7.5.0 or later.

· Additional details about online complex firmware updates can be found in the “HP Integrity Superdome X and Superdome 2 Onboard Administrator User Guide for HP”.

UPDATE RECOMMENDATION: Critical
HPE recommends systems used in Mission Critical environments update to this revision of firmware during the next system maintenance period in order to improve system reliability.
Note: Review the FIXES section to check if your system may be affected by the issue fixed in this release.

[X] Critical

[ ] Panic, [ ] Hang, [ ] Abort, [ ] Corruption, [ ] Memory Leak, [x] Performance, [ ] Security

[ ] Hardware Enablement, [ ] Software Enablement

[ ] Required

[ ] Recommended

[ ] Optional

[ ] Hardware Enablement, [ ] Software Enablement, [ ] non-critical

[ ] Initial Customer Release

SUPERSEDES:
Bundle 2015.09 (firmware version 7.5.0)

PRODUCT MODEL(S):
HPE Integrity Superdome X Servers

OPERATING SYSTEMS:
Supported OS’es on Gen8 blades:

SUSE Linux Enterprise Server 11 SP3, 11 SP4, 12 and 12 SP1
Red Hat Enterprise Linux 6.5 and future 6.x releases, 7.0 and future 7.x releases
Windows Server 2012 R2 (with Spring 2014 and November 2014 updates)
VMware vSphere 5.5 U3 and 6.0 U1

Supported OS’es on Gen9 blades:

SUSE Linux Enterprise Server 11 SP3, 11 SP4, 12 and 12 SP1
Red Hat Enterprise Linux 6.6 and future 6.x releases, 7.1 and future 7.x releases
Windows Server 2012 R2 (requires firmware version 7.6.0 or later)
VMware vSphere 5.5 U3 and 6.0 U1 (requires firmware version 7.6.0 or later)

LANGUAGES:
International English

FIXES:

nPartition firmware:

Superdome X systems with Gen9 blades installed and configured in 8- or 16-socket nPars, using 18 core processors (E7-8890 v3 or E7-8880 v3) and running Linux could experience a performance degradation. This is now fixed.

ENHANCEMENTS:

February 2016 updates:

Added support for VMware and for HPE Ethernet 560FLB/560M adapters on Gen9 blades

January 2016 updates:

Added support for Windows 2012 R2 and related IO drivers on HPE Integrity Superdome X Gen9 blades
Added support for Linux SLES 12 SP1 and RHEL 7.2

COMPATIBILITY/INTEROPERABILITY:

Note: See the Firmware Matrix for HPE Integrity Superdome X servers for latest information at
http://h20566.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=7161269&docId=emr_na-c04739260

IO cards
The following IO cards and versions are supported with Superdome X firmware version 7.6.0:

IO card	Gen8 Blades	Gen9 Blades	Supported OS’es
HP Ethernet 10Gb 2-port 560FLB and 560M Adapter	UEFI: 4.9.10	UEFI: 4.9.10	Linux, Windows, VMware
HP QMH2672 16GB Fibre Channel Host Bus Adapter	UEFI 6.37 FW: 8.01.42 BIOS: 3.31	UEFI 6.37 FW: 8.01.42 BIOS: 3.31	Linux, Windows, VMware
HP FlexFabric 10 Gb 2-port 534M and 534FLB Adapter ^1,2	UEFI 7.12.31 MFW: 7.12.83 PXE/MBA: 7.12.8	Not Supported	Linux, VMware
HP FlexFabric 20 Gb 2-port 630M and 630FLB card ^1,²	Not Supported	UEFI 7.12.31 MFW: 7.12.83 PXE/MBA: 7.12.8	Linux, Windows, VMware
HP Infiniband FDR 2-Port 545M Adapter	Not Supported	FW 10.10.50.52 UEFI 14.6.27	Linux only

NOTE 1: The HP FlexFabric 2-port 10GB 534M/534FLB and 20GB 630M/630FLB Adapters (Mezzanine and LOM) only provide Ethernet network support.
NOTE 2: FCoE is currently not supported with the I/O Adapters for HP Integrity Superdome X with BL920s Gen8 and Gen9 server blades.

Recommended I/O firmware:

When updating to Superdome X firmware version 7.5.0 or later, it is recommended to update the server IO firmware using the “HPE Integrity Superdome X IO firmware and Windows Drivers image” version 2016.01, available on the Superdome X firmware download page on HPESC. Select your OS and go under the “Software – CD-ROM” section.

Note:

After replacing an I/O adapter, check if a supported I/O firmware version is installed or update the firmware.
Offline firmware updates can currently be accomplished on smaller partition sizes only using the “HPE Integrity Superdome X IO firmware and Windows Drivers image” version 2016.01 (HPE recommends 1 blade only).
For additional details, consult with your HPE field representative.

Required I/O drivers:

· For servers running a supported Linux operating system, no additional I/O driver updates are needed. For supported OS details, refer to the Linux white paper “Running Linux on HPE Integrity Superdome X”.

· For servers running Windows operating system, if needed, the I/O drivers should be updated using the HPE Integrity Superdome X IO firmware and Windows Drivers image version 2016.01 as the update from the SPP with HP SUM is not working for the Superdome X server at this time. You can find the latest HPE Integrity Superdome X IO firmware and Windows Drivers image on the Superdome X for Windows 2012 R2 OS download page, under “Software – CD-ROM”. Follow the instructions in the bundle for installing the components.

· For servers running VMware, the I/O drivers should be updated using the appropriate async drivers which are available from http://vibsdepot.hpe.com/sdx/. Customers need to build their own custom VMware VSphere distributions. For details, please refer to the VMware white paper “Running VMware vSphere on HPE Integrity Superdome X” available at http://h20195.www2.hp.com/v2/default.aspx?cc=us&lc=en&oid=7161269

OS requirements

A. Linux

a. All Linux OS related information is available from the Linux white paper “Running Linux on HPE Integrity Superdome X”:

i. Check the HPE Servers Support & Certification Matrices for special OS requirements for the HP Integrity Superdome X Server

ii. Linux SMH and WBEM providers: HPE recommends that you install the latest versions of the SMH and WBEM providers for your SLES or RHEL Operating System from the Software Delivery Repository (SDR). Superdome X providers are available under http://downloads.linux.hpe.com/repo/bl920-wbem/
Note: You must install the SMH package prior to the WBEM providers or in the same session.
Note: Reboot is not required for the SMH and WBEM provider changes to take effect.

iii. Check the Linux white paper for additional details and recommendations.

B. Windows
I/O drivers and WBEM providers for Windows 2012 R2 for Superdome X are available as part of the HPE Integrity Superdome X IO Firmware and Windows Drivers image” version 2016.01 on the Superdome X download page on HPE Support Center, under “Software – CD-ROM”. Follow the instructions in the bundle to install the components.

For more information on installing Windows OS and components on Superdome X, see the Windows white paper “Running Microsoft Windows Server on HPE Integrity Superdome X”, available at http://www.hpe.com/support/superdomeXwindows-whitepaper.

C. VMware
I/O drivers and WBEM providers for VMware are available from this link: http://vibsdepot.hpe.com/sdx/downloads/feb2016.
For more information on installing VMware OS and components on Superdome X, see the VMware white paper “Running VMware vSphere on HPE Integrity Superdome X” available at http://h20195.www2.hp.com/v2/default.aspx?cc=us&lc=en&oid=7161269

PREREQUISITES:

WARNING:

If you are updating from a version prior to 6.0.42, you must install 6.0.42 (bridge release for digital signing) prior to updating to version 7.5.0 or later.

HPE strongly recommends implementing the following security best practices to help reduce both known and future security vulnerability risks:

1. Isolate the management network by keeping it separate from the production network and not putting it on the open internet without additional access authentication.

2. Patch and Maintain LDAP and web servers.

3. Run the up-to-date viruses and malware scanners in your network environment

4. Apply HPE Firmware updates as recommended.

INSTALLATION INSTRUCTIONS:

Please review all instructions and the "Hewlett Packard Enterprise Support Tool License Terms" or your Hewlett Packard Enterprise support terms and conditions for precautions, scope of license, restrictions, and limitation of liability and warranties, before installing this package. It is important that you read and understand these instructions completely before you begin. This can determine your success in completing the firmware update.

New Important Note: This version of HP SUM uses an Internet browser as the graphical user interface. Currently supported browsers are:

	Win2k8	Win2012	Win7	Win8	SLES11	SLES12	RHEL6	RHEL7
IE 9, 10 or 11	x	x	x	x
FireFox 17 ESR					x	x	x	x
FireFox 18 or later	x	x	x	x	x	x	x	x
Chrome 24 or later	x	x	x	x	x	x	x	x

New Important Note: HP SUM now uses port 63001 by default for pulling FW files from the server running HP SUM.

A. Extracting and Running HP SUM

1. Download the firmware bundle binary <filename>.exe or <filename>.tar.gz in a new folder on your system.

2. Extract the bundle:

Windows: double click <filename>.exe then click “Extract”
Linux: gunzip <filename>.tar.gz; tar -xvf <filename>.tar

3. The above steps will extract the contents of the bundle in the new folder where the bundle file is located. HP SUM and firmware components will reside in the same folder.

4. Execute hpsum.bat (Windows) or hpsum.sh (Linux), located in the extracted folder, by logging as a user with Administrator or root privilege. Executing hpsum will bring up your default browser to show the user interface of the HP Smart Update Manager (HP SUM).

NOTE: HP SUM also provides a Command Line Interface (CLI) that allows user to perform scripted installations in silent mode. For more information please refer to the HP SUM User Guide or the "CLIHelp.txt" file in the extracted folder.

B. Installing the Firmware Components using HP SUM - Graphical User Mode

1. Welcome Screen:

Once started, a page displays with HP SUM main content on it.

For remote OA based updates:

Select Baselines from the main content menu
Verify that the current directory baseline completes inventory
Select Nodes from the main content menu
Select 'Add Node' and enter IP address and credentials for the Onboard Administrator, select the Baseline to be assigned from the Baseline drop down, and click 'Add'
After initial verification of credentials is done, click Inventory from the Actions menu
After inventory is done on the OA, click on the OA node and start Review/Deploy
On the Review page, click to select the associated nodes to update along with the OA. HP SUM will sequence the updates as needed.
Start the Deploy
After Deploy is done, the logs for the updates can be reviewed on each node page

Note:

Online complex firmware update is supported starting with firmware version 5.73.0. For more details, refer to the online firmware update table and notes at the top of the release notes.
If doing an offline firmware update, you must power off all partitions before upgrading firmware to version 7.6.0 and then use the ALL option with the offline firmware upgrade to ensure that the partitions will boot with the new partition firmware after the update.
Additional details about online complex firmware updates can be found in the “HP Integrity Superdome X and Superdome 2 Onboard Administrator User Guide for HP”

· See the HP SUM user Guide for more information.

Reboot requirement:
Partition reboot is required after installation for Partition firmware updates to take effect.

DETERMINING CURRENT VERSION:

Establish a session with the monarch OA and login to the get the command prompt
Type the OA command "UPDATE SHOW FIRMWARE" to display the version of complex bundle installed.
Type the OA command “UPDATE SHOW NPARTITION ALL” to display the version of nPartition firmware installed on each partition.

KNOWN ISSUES & WORKAROUNDS:

An incorrect firmware version is reported in the standby OA GUI.
Workaround: run “show oa info” in the standby OA CLI to get proper version information.
When all blades in a partition are set to link local, the OA syslog reports the blades as powered off. However the OA CLI command "show blade list" reports the correct state.
If connected to the OA via telnet, the message “fatal: Cannot bind any address” may be seen in the OA syslog after running the command “disable ntp”, “disable https” or “disable snmp”. You may ignore this message.
OA users with operator privilege can enable or disable network protocols from the OA CLI. However they can’t do it from the GUI as the Network access section is missing.
In case of mismatch between XFMs and complex firmware versions, the OA CLI commands SHOW XFM STATUS/ SHOW XFM INFO do not flag the XFM as mismatched. Workaround: UPDATE SHOW FIRMWARE shows the mismatch.
Enclosure ID field in enclosure status may show as degraded after the DVD module has recovered from USB connectivity issues.
The monarch iLO in complex firmware version 5.73.0 or later is affected by the OpenSSL Poodle (Padding Oracle on Downgraded Legacy Encryption) CVE-2014-3566 vulnerability. More information can be found in this advisory c04496345.
If a user connects remote vMedia to a partition from the IRC applet, a “show partition dvd all” from the OA CLI will not report that the partition is connected to media via the “Virtual Media Applet”.
Java execution errors may be seen when launching the IRC (Integrated Remote Console) or RSC (Remote Serial Console) from the OA GUI, causing the applets to fail to launch, when using a Java Runtime Environment (JRE) other than the Oracle version.
Workaround: Remove or de-configure all java environments other than the Oracle version as this is the only JVM currently supported by iLO. The Oracle Java 7 JRE works correctly.
When more than one DIMM in a partition has been de-configured, the "partition status" and "pending changes" TABs on the OA GUI only show the first DIMM as de-configured. Refresh the OA GUI screen or use the CLI parstatus command to show correct information.
The OA “show blade info” command does not report a change in the blade “Asset Tag” value until after the partition is rebooted.
After a USB cable is reconnected between the OA and its matching GPSM (maybe due to a repair or lose connection), SHOW ENCLOSURE STATUS reports the Enclosure ID as "Degraded" instead of OK.
Workaround: Reboot the OA to clear the erroneous status.
When a blade is moved from a partition to another, the command SHOW BLADE INFO will continue to show the UUID from the prior partition until the new partition is booted to UEFI.
When using the Firefox browser, users may only use IRC for a single partition at a time as only one instance of the IRC client can be opened at a time.
Workaround: use Internet Explorer and the non-java based IRC client.
The parstatus command incorrectly displays the complex IO enclosure capacity as 8 instead of 0.
If a user performs an OA restart, OA failover or FW Update while an nPar is in OSBOOT state, the nPar state unexpectedly changes to UP state.
When an alternate parspec is created with default granule sizes, the parstatus –Z <parspec_name> command will display negative values (-1 MB) for granule size.
A side effect of the OpenSSL fix for CVE-2014-0224 is that OpenSSL gives a warning whenever the hostname field of the OA certificate does not match the hostname alias being used as the URL in the Web browser. This warning/alert may translate into an error on the client side if it is running versions of Java 7 or greater and can result in the client being unable to launch the Remote Serial Console, a live log viewer session, etc.
Workaround: You can avoid this problem by using the IP address specifically in the Web browser instead of an assigned hostname alias, or you can regenerate the certificate on the OA to specify the fully qualified hostname that the customer wishes to assign. Regenerating the certificate is a simple procedure, and it will not result in any required downtime for running nPartitions. The Active OA will reboot as a part of this process, and it will be necessary the clear the Web browser's cache (or completely restart the Web browser) after the OA has booted back up to an operational state.
Superdome X complex uses 169.254.x.x and 10.254.x.x addresses for internal management. Those addresses are visible to the outside LAN via “SNMPwalk”, which may cause incorrect reports of IP address conflicts. As a result, tools that use “SNMPwalk” to avoid IP address conflicts may refuse to use the 169.254.x.x or 10.254.x.x for other systems outside of the complex. Other than incorrect SNMP reporting, the internal management network traffic is contained within the complex and will not affect customer’s management network.
Note: The addresses 169.254.x.x and 10.254.x.x are not available to be used by the OA EBIPA.

DISCLAIMER:
The information in this document is subject to change without notice.

Hewlett Packard Enterprise makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett Packard Enterprise shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be reproduced, photocopied, or translated to another language without the prior written consent of Hewlett Packard Enterprise.

SUPERSEDES HISTORY:
Version 2015.09 (FW 7.5.0):
ENHANCEMENTS:

Superdome X server firmware version 7.5.0 introduced support for BL920s Gen9 blades
With firmware version 7.5.0, HP Integrity Superdome X Server supports multiple nPartitions of 6 sockets in addition to 2, 4, 8 and 16 sockets.

FIXES:

Excessive correctable memory errors could prevent an entire partition from booting. Boot attempts would fail with the error SFW_BOOT_FATAL_ERROR in FPL. This is now fixed.
False fabric errors or CAE event 2015 could rarely be seen after an EFI reset command or a non-graceful system shutdown, causing in some cases a critical error like an MCA, due to some packets not being discarded before power-on. This is now fixed.
A system nPartition would very rarely hang with the FPL (Forward Progress Log) or SEL (System Event Log) displaying some STATUS_ASSERT_* messages. This is now fixed.
The WSMAN daemon no longer crashes if a WSMAN client makes a subscription request with an unusually long “end point reference”.
SNMP no longer incorrectly sends trap 22041 whenever the active OA status changes.
On systems running SLES, Event ID 100924 would sometimes be erroneously reported for corrected memory errors. This is now fixed.
In case the monarch blade of an nPar is serviced and the Administrator does not wait long enough (about 5 minutes) before attempting to power on the partition, the partition no longer fails to power on with an error message in OA syslog “nPartition Power On failed. Error: fatal internal error”.
When removing an SNMP receiver’s IP address (ex. 10.11.12.13), OA no longer incorrectly removes all receiver’s IP addresses that contain that IP address as a substring (ex. 10.11.12.13 and 10.11.12.133).
A PDH low battery warning event is no longer reported daily in case of low PDH battery level. It is now reported yearly as an informational event.

The OA GUI now properly detects and displays a valid firmware bundle present on a USB stick in the external USB drive.

Version 2015.04 (FW 6.0.42):
ENHANCEMENTS:

Bundle version 6.0.42(a):

Added support for SUSE Linux Enterprise Server 12

Bundle 2015.04 (FW version 6.0.42):

Added support for Intel® Xeon® Processor E7-8893 v2 (6 cores/3.4Ghz / 37.5Mb cache / 155W)

FIXES:

Addressed the GHOST (GetHostByName) CVE-2015-0235 vulnerability
NTP was upgraded in this version to address the CVE-2014-9295 vulnerability
Addressed the OpenSSL Poodle (Padding Oracle on Downgraded Legacy Encryption) vulnerability CVE-2014-3566 in Superdome X OA
Fixed issues that prevented some Superdome X servers to be discovered by HP Insight Remote Support
Remote Windows Operating System installation may now be done using PXE boot (Pre-Boot eXecution Environment)
Fixed an issue where rebooting partitions without a power cycle could result in de-configured CPU sockets and/or blades and in a failure to boot
CAE event 7008 is now reported if multiple DIMM failures on the same DDR channel are detected during memory initialization at partition boot
Erasure is no longer requested multiple times for the same failing device
In the OA GUI, after selecting ""Local User" and then "User information", Interconnect Bay Access is now shown for all bays, including Bay 5 to Bay 8
An Onboard Administrator board with firmware version 1.3.1 can now be updated to the latest version using the standard firmware update process

Version 2014.10 (FW 5.73.0):
ENHANCEMENTS:
Changes included in bundle 2014.10 (FW version 5.73.0(b)):

Added support for Windows 2012 R2 with minimum Superdome X server firmware 5.73.0

Changes included in bundle 2014.10 (FW version 5.73.0(a)):

The release notes were updated in version 5.73.0(a), to add the Poodle security vulnerability to the list of Known Issues

Changes included in bundle 2014.10 (FW version 5.73.0):

Starting with firmware version 5.73.0, the HP Integrity Superdome X Server supports 2S, 4S, 8S and 16S nPartitions. For information about creating and managing partitions, see the HP Integrity Superdome X partitioning white paper under the Superdome X server Manuals section on http://www.hp.com/go/hpsc.
Note: Maximum 4 TB memory is supported with Windows (see server QuickSpecs for more details)

FIXES:
Fixes included in bundle version 2014.10 (5.73.0(a), 5.73.0(b)):

None (release notes update only)

Fixes included in bundle 2014.10 (FW version 5.73.0):

The bash “Shellshock” vulnerability has been fixed in the OA version included in this firmware. Firmware versions prior to 5.73.0 could be exploited remotely to allow execution of code. For details on this issue, please refer to CVE-2014-6271, CVE-2014-6277, CVE-2014-6278, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187.
Addressed SSL/TLS MITM Vulnerability CVE-2014-0224
During boot, the partition fans would unnecessarily run at maximum speed, making the enclosure very noisy, until partition completed boot to UEFI.
Correctable errors coming from multiple failing ranks on a single DIMM could inadvertently result in the entire Blade being indicted (even 7005).
If a partition was forced to power off, stale data from the prior session would sometimes be displayed on the console when the partition was powered back on and remained visible until it began booting. These stale data could be ignored.
The OA CLI did not allow setting the EBIPA (Enclosure Bay IP Addressing page) for interconnect modules. The operation failed with the message "Cannot issue command for non-monarch blade".
After an OA restart or DVD replacement, the DVD health LED would often be seen amber and blinking. If the command “SHOW DVD status” or related views reported the status as “OK”, you could safely ignore the amber blinking LED.
A transient USB connection would sometimes generate transient errors and an event DVD/GPSM_MODULE_USB_DISCONNECT (CAE id 12119). This event could safely be ignored if the complex was not marked as degraded and no hardware was indicted.
If you tried connecting the enclosure DVD from the CLI using the command "set partition DVD connect <npar>", with a remote DVD media already connected via GUI using iLO IRC to the same partition, the CLI command did not return a failure message saying that the same type of DVD drive was already connected.
There were several issues with the UEFI shell 2.0 behavior. In particular, the command option –b (page break) did not always work correctly. The prompt “Press ENTER to continue or ‘Q’ break” could be inserted in the middle of output text instead of starting at a new line or overwrite text that should have been displayed on the next line.
When a blade was removed slowly from the chassis, global clock failure events (CFW_GCLK_0_NOT_AVAIL and/or CFW_GCLK_1_NOT_AVAIL) would rarely be generated prior to the blade removal event (BLADE_REMOVED_SD2) due to noise on the clock signal caused by the removal. These clock failure events could safely be ignored during blade removal.
After making a PXE boot request, if the user decided not to proceed with PXE boot (e.g. “exit” from the PXE menu to return to the UEFI prompt), any attempt to boot would still result in PXE boot regardless of what the user selected, because the PXE driver was still loaded.

FEEDBACK
As we are continuing to improve the firmware management process we welcome your feedback on this document and on the firmware update process: TEAM-FWupdateFeedback@groups.ext.hp.com