TITLE: HP Integrity Superdome 2 Server and I/O Firmware Bundle - for HP Smart Update Manager

VERSION: 
HP Smart Update Firmware Bundle
Bundle Version: 2013.04

Complex Firmware Bundle Version: 3.7.14

I/O components versions:

Firmware Flash for Add-in Smart Array Adapters: 2013.02.18
    P411: ROM 6.22
    P812: ROM 6.22

Firmware Flash for Qlogic Fibre Channel Host Bus Adapters 2012.11.30:
        1-port/2-port 8 Gb FC AH400A, AH401A: ROM 5.03.15, EFI 2.22

Firmware Flash for InfiniBand Adapters 2012.11.30:
   HP 4X QDR Infiniband (592519-B21): 2.9.1000

Firmware Flash for Emulex Adapters 2013.02.18:
     1-port/2-port 4 Gb FC + 1000BT AD221A, AD222A, AD393A: FC ROM:  2.82x4, FC EFI:  4.01a5 
     1-port/2-port 8 Gb FC AH402A, AH403A: ROM:  2.02x2, EFI: 4.01a5
     2-port CN1000E AT111A: LAN & FC ROM:  4.1.450.14, LAN EFI:  2.21AC, FC EFI: 5.02A4
     8 Gb FC/10 Gb LAN AT094A: LAN ROM: 4.2.401.20, LAN EFI:  2.22A0 , FC ROM:  2.02x2 , FC EFI:  4.01a5 
     NC552SFP 10Gb Flex-10 AT118A: ROM:  4.1.450.14 , EFI:  2.21AC

Firmware Flash for Intel and Broadcom Adapters 2012.11.30(b):
    Superdome 2 embedded LOM: EFI 5.2.59, ROM 6.2.25   
    2-port 10 GbE AM225A, AM232A, AM233A: EFI 5.2.59, ROM 6.2.25   2-port/4-port 1000B-T/SX AD337A, AD338A, AD339A: EFI 4.3.01
    4-port 1000B-T + 2-port 1000B-SX AD393A: EFI 4.3.01
    1-port/2-port 4 Gb FC + 1000BT AD221A, AD222A, AD393A: LAN 4.3.01

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

DESCRIPTION:
This bundle contains the firmware for HP Integrity Superdome 2 Servers with HP Smart Update Manager (HP SUM) application - which includes Complex and nPartition firmware and as well as Superdome 2 I/O firmware.

Notes:

• Complex firmware version must be equal to or higher than the nPartitions firmware version at all times.
• Minimum OS and Firmware requirements per blade type with Complex Firmware version 3.6.48 and later:
• Partitions containing CB900s i4 blades (with Intel Itanium 9500 series processors) must run HP-UX 11i v3 September 2012 or later and both the Complex and nPartitions must run firmware version 3.6.48 or later.
• With complex firmware version 3.6.48 or later, nPartitions must run firmware version 2.53.0 or later and HP-UX 11i v3 September 2011 update or later on CB900s i2 blades (with Intel Itanium 9300 series processors).
• Mixed firmware versions support:
• After updating complex firmware to 3.6.48 or later, partitions on CB900s i2 blades can continue to run 2.53.0 nPartition firmware and the complex can have a mix of nPartition firmware version 2.53.0 and later versions active at the same time.
• Rolling upgrades:
• Servers with complex firmware version 1.3.0 or 1.3.1 require bringing down the entire complex to perform the firmware update.
• Servers with complex firmware version 2.2.27 or later and running HP-UX 11i v3 September 2011 update or later can be updated online without the need to bring down the complex. A partition reboot must be scheduled when convenient to activate a new nPartition firmware.
• You may update the complex and all the nPartitions firmware at the same time.
• If you plan to update the nPartition firmware later, make sure that your intermediate combination of complex and nPartitions firmware is supported.
• For details on supported combinations of Complex and nPartition/OS firmware versions and features supported in each combination, refer to the table under the Compatibility section.
• Firmware update process notes:
• Partition Firmware in bundles 3.6.48 and 3.7.14 is identical. When updating from 3.6.48 to 3.7.14, the Partition Firmware version reported will be updated to 3.7.14 if Partition Firmware is selected for install, but no partition reboot is required.
• If LLF (Link Loss Failover setting) is enabled and a loss of link occurs on the active OA during a firmware update from complex version 2.53.0 or earlier, blades can be left in an unusable state. Workaround: Disable LLF prior to a firmware update using the OA CLI command "disable LLF" and re-enable LLF upon completion using the OA CLI command "enable LLF”
• For gWLM users, it is recommended to stop gWLM while performing an online update.
• If running Business iCAP software, you must update to Managed iCAP. See dependencies under Pre-Requisites. For more details on the iCAP upgrade, please refer to the white paper ‘Upgrading to HP Instant Capacity with dynamic cores on HP Integrity Superdome 2 servers’.
• When updating active IOX enclosures from a version 2.53.0 or earlier, the update will be partial until each IOX can be updated after shutting down affected partitions.  It is supported to run indefinitely in the partially updated (Mixed) state.  IOX enclosures in this state will not have the increased thermal tolerance introduced in version 3.6.48. To complete the update, you must shutdown all partitions using an IOX and then reapply the firmware update to the complex only (not to the nPartition). This update will only target the IOX device(s) and will be much faster than a full complex update.
• When updating to this release from 2.2.27 or earlier, Socket Level Memory (SLM) values for nPars that have not been explicitly set i.e. still have default factory values, will be set to 0. In order to easily recover these values, before the update, document your Interleaved Memory (ILM)/SLM settings using the parstatus command. After the update has completed, reset the values using the parmodify command.
• Firmware update can be performed using HP SUM or from the OA CLI or GUI.

Refer to the HP SUM User Guide and Release notes for more information.

UPDATE RECOMMENDATION: Recommended

HP 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.
[ ] Critical
    [ ] Panic, [ ] Hang, [ ] Abort, [ ] Corruption, [ ] Memory Leak,
    [ ] Other
    [ ] Hardware Enablement, [ ] Software Enablement
[X ] Recommended
[ ] Optional
    [ ] Hardware Enablement, [ ] Software Enablement, [ ] non-critical
[ ] Initial Customer Release

SUPERSEDES:  

Complex Firmware Bundle Version: 2012.12(b) (3.6.48)

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

PRODUCT MODEL(S):
Superdome 2 – 8s
Superdome 2 – 16s
Superdome 2 – 32s

OPERATING SYSTEMS: 
- HP-UX 11i v3 September 2011 update (or later) is required to support his firmware with CB900s i2 blades only
- HP-UX 11i v3 March 2012 update
- HP-UX 11i v3 September 2012 update or later is required to support this firmware with CB900s i4 blades

NOTE: The HP-UX nPar commands “parcreate”, “parmodify”, “parstatus” and HP-UX vPar commands “vparmodify”, “vparstatus”, “vparcreate”, “vparresources” are updated and in sync with updated firmware parcon partitioning commands, however the corresponding HP-UX nPar man pages  will be  updated starting with the HP-UX 11i v3 March 2013 update and HPUX vPar man pages will be updated in a patch to be released before 31 March 2013. If you are using an HP-UX version prior to the March 2013 update or without the HPUX vPar man page patch, refer to the corresponding OA help text instead of the man pages.

The HP Integrity Superdome 2 Errata and patches are available here.

LANGUAGES:

International English

ENHANCEMENTS:

SD2 Version 2013.04 (3.7.14): 

• Improved error resiliency on fabric links 

UEFI Driver 5.2.59 (from 5.2.58) for embedded LOM, AM225A, AM232A, AM233A:

•  Added Dynamic Network detection support

FIXES: 

SD2 Version 2013.04 (3.7.14): 

• A failed fabric link now results in the complex-level fabric status showing as degraded instead of remaining as OK while the “Xfabric link status” field of the “show xfm status” or “show iox status” command was showing the link as Failed.
• If an XFM module cannot be powered on as part of a complex initialization, "show complex status" now shows as DEGRADED instead of OK and the powered off XFM module will be de-configured until the next complex initialization.
• Upon a cell replacement or upgrade, warranty and entitlement information is no longer migrated from the original blade to the replacement blade.
• The "show enclosure power_summary" command no longer shows 549W more power than is actually allocated in "Power Allocated" on a per blade basis.
• Fixed a firmware issue which could result in the OA reporting erroneous failures like “unexplained firmware mismatch”, or grayed-out display on the “Insight Display” page, or a firmware update failing with the error "Firmware update cancelled by system”, and where the user had to restart the OA to fix the issue.
• Vparstatus no longer shows more cores than expected if vparmodify is run with the option “-m cpu::<num>” or “-m core::<num>” while the vpar is down and if that vpar already has some SLP (Socket Local Processors) or cores added by path.
• On a Superdome 2-32s system with blades in different slots in each enclosure, the ParGUI partition status page no longer displays some blade product names as "[Unknown]".

SAS 6.22 (from 5.78):

• HP Integrity Smart Array P411 and P812 Controllers, running version 5.78 or lower and connected to Superdome 2 servers may, under extremely rare conditions, silently return stale or out-of-order data. For more details, please refer to c03689769.

• With HP P411 or P812 controllers installed in a Superdome 2 server and external RAID connected, no post message is printed if “reconnect --r” is used to list cards at EFI shell. However during reboot, when selecting “s” at boot menu in EFI shell, post messages are printed. This is a generic issue and not specific to any server.
• HP-UX boot may fail with READ Error (elf_load) if boot volume is built on SAS Logical Volume larger than 2TB

Boot Code 6.2.25 (from 6.2.21) for embedded LOM, AM225A, AM232A, AM233A:

• In some cases, only 2 PCI functions are exposed in multi-function mode.

AT094A Lan FW  4.2.401.20 (from 4.1.450.14) fixed issues:

• Boot failure might be seen after running commands "reconnect -r", "map -r" commands at EFI environment.
• Boot from SAN intermittently fails during EFI bootstrap of a FCoE device that is busy.
• FCOE EFI version truncated in VPD data displayed by ODE-FCFUPDATE tool at EFI.
• On HP-UX, the fcoc port driver state is displayed as AUTHENTICATION/DISCOVERY when fcocutil command is run to check the port information.

AT094A LAN UEFI Driver 2.22A0 (from 2.21AC) fixed issue:

• BL8x0c i4 LOM Product Name is truncated when displayed from NIC interface using FCFUPDATE.

HBA FC FW version 2.02x2 (from 2.00a4) for AT094A, AH402A, AH403A:

• I/O “illegal frames received” errors may be reported intermittently by FC disks linked through an 8Gb Hp/Emulex FC card if a disk reset is performed during heavy I/O load.

Note: For I/O components’ enhancements and fixes, please refer to the I/O components’ release notes. Links to the I/O component firmware packages can be found in the HP Release set for Superdome 2 servers.

PREREQUISITES :

Complex firmware version 3.6.48 or later, with all nPartitions running firmware version 2.53.0 or later and HP-UX 11i v3 September 2011 update or later, supports the following features, which may require additional software (see Related Software below and Pre-Requisites below):

• Dynamic Cores vPars
• Dynamic Core Migration (with gWLM)
• Dynamic Processor Resiliency (DPR)
• GiCAP (Global Instant Capacity)
• Locality Optimized Resource Management (LORA)
• Rolling upgrades

RELATED SOFTWARE:

The following software is required to use the associated functionality:

• HP Matrix Operating Environment 7.1 Update 2 - includes the minimum version of gWLM (Global Workload Manager) for supporting Dynamic Cores
• Global Workload Manager (gWLM) with patch PHSS_43165 installed on a managed node on top of gWLM Agent of HP MOE 7.1 Update 2
• Dynamic Cores vPars A.05.09 or later
• HP-SIM 7.1 Update 2
• Insight Control Power Management 7.1 Update 2
• GiCAP (Global Instant Capacity) Group Manager and partition-resident iCAP software (released in the HP-UX 11i v3 December 2011 update) which require the updated HP WBEM Services for HP-UX version A 2.09.14 and GiCAP rule file version 2.19.
• Pay-per-use (PPU) requires the Utility Meter 9.4 or higher to enable dynamic cores support.

See the individual software release notes for Related Software information.

•  HP-UX 11i v3 September 2011 update (or later) is required to support this firmware.  The following HP-UX patches (or superseding) must be installed when running on partitions with 2.51.102 or later nPartition firmware.
• PHKL_41942 (enable CPU OL*)
• PHKL_42482 (enable CPU OL*)
• PHCO_42306 (enhancement for machinfo)
• PHKL_42230 (strongly recommended)
• PHKL_42314 (strongly recommended)

• With this firmware, if the  HP-UX version is HP-UX 11i v3 September 2011 update or HP-UX 11i v3 March 2012 update:
• An updated WBEM bundle is required to be installed to add a member Complex to the GiCAP group.
• An updated SFM bundle is required to send actionable events (with alert level greater than Warning) and test events to the Error Analysis Engine.

                 The updated WBEM bundle and SFM bundle is part of September 2012 web release of WBEM Management bundle (version C.05.01 or later) and can be installed from:

                   https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=WBEMMgmtBundle

Note: HP-UX 11i v3 September 2012 update already contains the updated WBEM bundle and updated SFM bundle.

• With this firmware, if the HP-UX version is HP-UX 11i v3 March 2012 update or HP-UX 11i v3 September 2012 update, an updated SFM bundle is required to be installed to get the One Stop Fault Management functionality and to handle the new positive return values. This bundle is part of September 2012 web release of WBEM Management bundle (version C.05.01 or later) and can be installed from:

            https://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=WBEMMgmtBundle

Note: HP-UX 11i v3 September 2011 update does not support the One Stop Fault Management functionality

• For Superdome 2-32S configurations, HP SIM support requires patch version SIM 6.3 Update 1 or higher
• Dynamic core migration with gWLM & iCAP enablement requires:
• HP Matrix Operating Environment  7.1 Update 2 or higher
• Global Workload Manager (gWLM) with patch PHSS_43165 installed on a managed node on top of gWLM Agent
• Pay Per Use (PPU) with Utility Meter 9.4 to enable dynamic cores support
• HP Instant Capacity version 10.06.01 or later

For information on supported I/O firmware versions, please refer to this Matrix:

HP Release Sets for Superdome 2 servers

INSTALLATION INSTRUCTIONS:
Please review all instructions and the "Hewlett-Packard Support Tool License Terms" or your Hewlett-Packard 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.

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, located in the extracted folder, after logging in as a user with Administrator or root privilege.  Executing hpsum will bring up a graphical 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:
1. Once started, a page displays with HP SUM introduction content on it. The introduction describes HP SUM, its usage, enhancements (if any), and EVA bundle information.
2. Source Selections screen:
1. The Source Selections screen allows you to choose directories where smart components are located.
2. The directory where HP SUM is running from is automatically added as the default repository.
3. You can optionally have HP SUM check ftp://ftp.hp.com/ for additional firmware or software smart components.  This could include newer components for servers supported in this bundle, plus components for other server types.
4. HP SUM will build an inventory of firmware bundles - packages that can be used to update firmware.
5. Click the "Next" button to move on to the next step.
3. Select Targets screen:
1. This screen is used to specify which targets you want to update.
2. Targets can be added one at a time, or a range can be searched.
3. Credentials must be supplied for each target.
4. Once added, targets can also be managed in groups.  See the HP SUM User Guide for details.
5. Click the “Next” button to move on to the next step.
   NOTE for enclosures:  The Onboard Administrator IP can be added as the first target and HP SUM will find all of the servers and Virtual Connect in the enclosure automatically.  A pop up dialog will appear suggesting to add the found associated targets.  HP SUM will be able to use the OA credentials to log into the blades iLOs automatically.
   NOTE: “localhost” is not applicable for installing the firmware updates included in this bundle.
4. Review/Install Updates screen
1. The suggested updates for each target are displayed on this screen.
2. This screen also allows the following actions:
1. Retrieving details of the updates.
2. Selecting between available revisions.
3. Forcing downgrades.
4. Choosing reboot to activate options
3. For more details and component level granularity, select the item and click the "Select Components" link.
   NOTE: If firmware is the latest or already up-to-date version, HP SUM displays the message "Already-up-to-date". You can override and choose to perform force reinstallation or downgrade the firmware by clicking the "Installation Option" and checking “Force Install” option.
   NOTE: Integrity System Firmware Update supports delayed activation - where the new firmware gets downloaded to the iLO but is programmed only when you power down the system at a convenient time. Delayed activation is the default setting for SFW update. This setting can be changed by doing the following actions
1. Click "Configure Now" on the Select Components page
2. Select the "Upload and Activate" checkbox.
1. If "Upload and Activate" is selected, HP SUM will do the following actions:
1. Send a graceful shutdown and power off request to the system as part of the update
2. Then power up the system after the System Firmware has been programmed.
2. If you choose to do the power off manually, the programming operation will take approximately 8 minutes to complete before power can be turned on again.
   NOTE: Integrity Superdome 2 nPartition firmware updates can be applied while the partition is Active, but the partition must be rebooted to have the firmware update take effect. HP SUM defaults to not reboot Active partitions.  If you would like HP SUM to include the partition reboot as part of the firmware update process then do the following actions: 
3. Click “Select Devices” on the Select Components page
4. Click “Reboot to Activate” next to the Active partitions you  want to reboot.
4. If you choose to not continue with install on one or more targets, you can uncheck the box on the left of the target.
5. Updates can be scheduled for future times by clicking the “Schedule” button. Once schedules are defined, the “Install” button must still be clicked to activate the schedule.
6. Click the “Install” button to start update on all of the checked targets.
7. HP SUM will display the progress of the firmware update on each target.
8. A status and link to the logs will be displayed for each target at the end of the update.  

Refer HP SUM 5.3.5 User Guide and Release notes for more information.

COMPATIBILITY/INTEROPERABILITY:

• WARNING:Do not disconnect AC power to HP Integrity Servers or remove HP Server Blades from the enclosure during the firmware upgrade process. Doing so may corrupt the programming of the firmware, rendering the Server inoperable.
• The following firmware/OS combinations are supported:

• Note 1: No PCIe OL* support (requires 3.6.48 or later partition firmware)
• Note 2: A partition reboot of existing partitions is required to update the FPGA to get new IOX thermal limits.  The update must be reapplied while each partition is down to complete the update of the IOX enclosure.  See Notes in the Description section above and Known Installation Issues below for additional information.
• Note 3: Supports PCI OL*, but won’t have the following functionality (only enabled with September 2012 or later):
• Improved I/O performance in virtual environments
• Added fault isolation assistance to the proper FRU for some catastrophic errors
• Support for Cisco B22HP Fabric Extender and B22HP Fabric Extender with 16 FET (stand alone only)
• Note 4: One Stop Fault Management is not supported on HP-UX 11i v3 September 2011 update
• Note 5: Partition Firmware in bundles 3.6.48 and 3.7.14 is identical. When updating from 3.6.48 to 3.7.14, the Partition Firmware version reported will be updated to 3.7.14 if Partition Firmware is selected for install, but no partition reboot is required.
• Complex firmware can be updated and activated while the complex is online as long as both the “before” and “after” combinations of firmware/OS are supported.  From a visual viewpoint, complex firmware can be updated online as long as the two configuration boxes (“before” and “after”) in the same column indicate "Yes"
• As noted, a partition reboot and repeat of the firmware update is required to activate the new IOX thermal thresholds.
• Partition firmware can be installed while the partition is online.  However, a partition reboot is required to activate the new partition firmware

• The following recommendations are in place for optimizing PCI OLRAD performance:
• Customer Requirements to enable support for PCI OL*
• Customers will be required to run Superdome 2 system firmware release 3.6.48 or later
• Customers are required to install the following patches (or their current replacements) to fully support PCI OL* with HP-UX 11i v3 September 2011 update with system firmware release 3.6.48 or later:
• PHKL_42230    1.0            kernel access infrastructure cumulative patch
• PHKL_42314    1.0            TLB,MCA Recovery,HPVM,NUMA,P-State,IPMI,OsName,GPE
• PHKL_42331    1.0            EFI Cumulative patch
• PHKL_42482    1.0            ACPI CA cumulative patch
• HP strongly recommends for optimal performance for OLRAD functionality, customers also install the following patch: (required for 11i v3 September 2011, March 2012 and September 2012 updates)
• PHCO_42997                1.0            olrad(1M) cumulative patch
• For HP-UX 11i v3 March 2012 update and September 2012 update, no additional patches required
• While not directly related to OLRAD functionality, HP recommends all customers install or ensure the following list of additional patches are on their HP-UX 11i v3 September 2011 update and March 2012 update systems to ensure optimal performance and stability for OLRAD
• PHKL_41942 (enable CPU OL*) : included with 11i v3 September 2011 update cold install
• PHCO_42306 (enhancement for machinfo)
• Note: PCI OL* is supported in vPars v6 and HPVM environments with very limited capabilities.

DETERMINING CURRENT VERSION:

• Establish a telnet session with 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 :

• XFM Exhaust Critical Temp Threshold value getting corrupted.
  Workaround: None Required
• update show nPartition can fail to read the configured firmware version
  Workaround: Since this issue is intermittent, repeating the command may return the correct information. The SHOW BLADE INFO command will also return the nPartition firmware version for each blade in the partition.
• The connection to the system console logs is lost after hitting CTRL-c.
• Java Runtime Environment (JRE) must be installed on the client system to view the remote serial console screens

• XFM links might show as unknown after running the ‘force takeover’ command from the OA CLI.

• After updating firmware from 1.3.x to 2.2.27 or later, you cannot delete IO slots 6 & 7 (USB and ILO) from the vPar.
  Workaround: The ILO and USB slots should be removed from vPars that currently own these resources BEFORE updating to 2.2.27 or later.
• When adding privileges to a user or group account via the OA GUI, only the first enclosure’s Server and IO Bays are displayed for selection.  This issue only impacts systems with multiple enclosures (32-socket systems).  Since Superdome privileges are assigned on a partition basis, not a Server or IO Bay basis, there is no effect on system operation.
• When a Fabric configuration change needs to be propagated across partitions and blades, and one of the nPars is a single blade nPar where the blade is missing, FAB_DAEMON_ERROR is generated.  There is no impact to performance or functionality.
• If you stop a link used by an active partition, poweroff/poweron the partition, start the link in HR, then stop the link in HR, the stop will fail.  Instead, either restart the stopped link before rebooting the partition or reboot the partition after restarting the stopped link but before stopping the link again.
• Rapid navigation through the partition pages can result in incorrect content being displayed.  Please wait for pages to load completely before navigating away to another tab.
• When a user navigates from Create nPartition to Modify nPartition, fields in the Modify nPartition page can end up displaying empty fields.  Select the newly created partition from the left navigation menu and click on the Modify button on the Status tab to update the blank fields.
• vPar state handling gets stuck in INIT when a TOC is issued on the vPar while it is activating.  Force a reboot or shut down the vPar to recover the state.
• An nPar can get stuck in the reboot state if a TOC is issued on the nPar and a reboot is issued before the TOC completes.  Workaround:  Force a power off on the nPar.
• If a blade is left in a bad state after an online firmware update, the GUI does not provide enough information to diagnose the problem.  The OA CLI command “show update firmware” can provide additional information.
• Under conditions of very high, unnatural stress involving reboot cycles and core license and assignment migration, some core movement requests may fail.  An example scenario would be a User running an OL* operation via a script in a stressful way, issuing both icapmodify and vparmodify commands on the same vPar.  The problem is resolved by retrying the failed request.
• If a vPar does not have SLM (Socket Local Memory) assigned to it, the SLM field under “Memory Details” from the vparstatus --v command is blank.
• Upon the rapid issue of multiple parallel vparcreate commands on the same nPar, one of the commands may fail.  This failure is typically encountered when a script is created to issue multiple vparcreate commands in rapid succession.  It is advisable to insert a delay of 1-2 seconds between successive vparcreate commands in scripts to avoid facing this issue.
• On systems with complex partition version 3.6.48 or 3.7.14 (bundle 2012.12 or 2013.04), users logged into the OA via an LDAP group will be unable to successfully complete any action requiring partition access verification (for instance, running a parcon command or connecting to a partition). These actions will fail with an insufficient privilege error.
  Workaround: Use a local OA user account with proper permissions instead of logging via an LDAP group.
• On SD2-32s servers, in the OA GUI Modify nPartition screen, the Blade Resources section displays wrong enclosure’s blade data for one enclosure as both enclosures images show the blade data from the same enclosure. This may lead to assigning incorrect blades to partitions.
  Workaround: Use the CLI to assign blades to partitions instead of the GUI, or verify first which blades are present using the OA GUI Complex Information screen.
• When attempting to power off an existing partition from a user account that either doesn't have OPERATOR or higher access rights and/or has not been assigned access to the partition, the command will not be executed, but no error message will be displayed to indicate that the request failed.

Known issues and workarounds related to PCI OL* :

• PCI OL* is supported in vPars v6 and HPVM environments with very limited capabilities.
• For Superdome 2 customers using Infiniband, to use PCI OL*, customers must install the IB4X-00 product from the HP-UX 11i v3 March 2012 update or later release media.
• Because of PCI OL* enablement issues found with several of the HP-UX IO drivers, customers must install:
• HP-UX 11i v3 September 2012 update IO drivers.
• Note;  HP-UX 11i v3 September 2012 update or later drivers can be installed on HP-UX 11i v3 September 2011 update and March 2012 update, without having to install anything else from HP-UX 11i v3 September 2012 update or later.  Customers should visit software.hp.com for the latest driver release packages which may have important updates.
• Web Release 1209 SFM and IO Providers

KNOWN INSTALLATION ISSUES: 

• The ‘show update firmware’ OA command may report a FRU(s) firmware mismatch after updating from system firmware version 1.3.1 to version 2.51.102 or later. Reapplying the update will solve the mismatch (the second update will be much faster as it will only update the metadata).
• When performing an online update with active partitions which include resources in IOX enclosures the system will report the following warning.  This warning incorrectly states the resulting configuration is mismatched and unsupported.  The IOX enclosures which are affected will actually be reported as "Mixed", which is a supported configuration.  A sample warning message is listed here.  This message will be followed by a list of active IOX enclosures to which it pertains.
• Warning: The boards listed below contain components which may not be updated until the partitions using them are shut down. This update operation will proceed but certain components on these devices will not be updated and the system will have mismatched firmware after the operation completes. The system will not be supported until all firmware mismatches have been resolved.
• HP SUM fails on Windows due to McAfee firewalls. This is a known issue with McAfee that McAfee firewalls block HP SUM traffic.

     To resolve this issue, enable the port traffic associated with the HP SUM application by performing the following steps:

1. Bring up McAfee Host Intrusion Prevention
• Windows Vista: From the system tray, click the McAfee icon -> Manage Features -> Host Intrusion Prevention
• Windows7: From the system tray, right click Host Intrusion Prevention icon -> Configure
2. Select the Activity Log tab. Notice the entry in the Message column similar to the following: Blocked Incoming TCP from the HOST (x.x.x.x) during execution of HP SUM.
3. Select the Firewall Policy tab.
4. On the bottom of the screen, click Add (Add new rule).
5. Use the following settings for the new firewall rules on your system.
          Action: Permit
          Protocol: IP - TCP
          Direction: Incoming
          Local Service: Single - http
          Remote Service: Range From: 1024 - To: 65535
          Address: Any Active
6. Click OK to ensure new firewall rules have been implemented.
7. Restart HP SUM.

• In some cases, target HP-UX nodes may hang in the "Discovering…” state.  If this happens, the target should be unchecked and the I/O FW update must be completed via a pre-HP SUM process.
• Do not use the “Reboot Now” button which appears after installing both an HP-UX target and its associated iLO in the same session, or the local machine running HP SUM may be rebooted unexpectedly along with the target system(s). Note: The “Reboot now” button only appears if you have not selected “Reboot to activate”.
• Alternatives are to use the option “Reboot to activate” before initiating the update so that HP SUM automatically reboots the target systems, or to manually reboot the target systems instead of using the “Reboot Now” button.
• The error message "Unable to start hpsum session on remote target" may appear after adding a valid HP-UX target. One reason may be that the pciinfo module status has been changed. You may run the command "kcmodule --b yes -s pciinfo=best" and then retry adding the target.
• If a target appears to hang with the status "Waiting for update on the associated host", exit HP SUM and restart the update on just that target.  This can happen if updates are attempted on OA, iLO and HP-UX all in the same HP SUM session.  The recommended update procedure is to update OA and iLO together in one session, then exit and update HP-UX I/O FW in a separate HP SUM session.
• If you receive the message "Could not add the following requested repositories:" after selecting a directory to use with HP SUM, the HP SUM temporary directory must be removed and then HP SUM must be restarted.

• Windows: From a command prompt enter: rmdir /S %temp%\hp_sum
• Linux: From a shell prompt enter: rm --rf /tmp/hp_sum
• If you receive the message "Connected to unknown SOAP server" while connecting to targets, another program is probably blocking HP SUM from using SSL port 443, close the other applications and try again. If the problem persists, please exit HP SUM and log out and log back in to clear any background processes that may be blocking HP SUM.

      Refer to the HP SUM 5.3.5 Release Notes for complete list of known HP SUM installation issues.

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

Hewlett-Packard 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 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 Company.

(C) Copyright 1994-2013 Hewlett-Packard Development Company, L.P.

SUPERSEDES HISTORY:

Bundle Version 2012.12

ENHANCEMENTS:

• Superdome 2 servers now support CB900s i4 blades containing Intel Itanium 9500 Series processors  in addition to the already supported CB900s i2 blades (with Intel Itanium 9300 Series)
• Support for 8GB Low Voltage DIMMs on CB900s i4 blades. – Up to 4TB per OS image
• PCIe OL* support for CB900s i2 and CB900s i4 blade partitions – Add, Replace or Delete IO cards without partition downtime
• New One Stop Fault Management solution for Superdome 2 platforms, allowing single point of access for all hardware failure indications
• Additional Error Analysis capabilities

New Onboard Administrator Management features

• Per-Partition User Authorization – User rights may be restricted to access per individual partition
• Enclosure IP Reduction – Reduces the demand for external IP addresses for blades
• Archive Storage – Internal storage capacity for firmware images, configuration scripts, and other data
• Partition Configuration Backups – Enables disaster recovery protection for the complex partition configuration

IOX enclosure thermal thresholds and actions are now consistent with the compute enclosure limits

FIXES: 

• Interleaved or Socket Local Memory (ILM or SLM) added to a vPar are no longer lost if iCAP authorization fails on vPar boot.
• Blades are no longer left in an unusable state if Link Loss Failover (LLF) is set and a loss of link occurs on the Active OA during a firmware update.
• ILM (Interleaved Memory) and SLM (Socket Local Memory) values are no longer automatically reassigned when switching between nPars and vPars mode.
• During an OA reboot, if an ILO/VGA port is reported but not present, the OA will go into a continuous reboot loop. This behavior is now fixed.
• Some PCIe errors might cause a local MCA which might in turn cause a global MCA. This behavior is now fixed.
• vPar no longer gets into a hung state if a CPU migration is cancelled by an unknown entity.
• If an OA restart is done while some nPars are active, parstatus -p -V now displays the firmware revision for the active partitions.
• Fixed an erroneous amber LCD display following an upgrade from Superdome 2-16s to Superdome 2-32s.
• One large nPar exhibiting a blade failure will no longer cause a resource issue, preventing all vPars configured in the partition from booting.
• Corrected indictment errors erroneously reported for blade 255.
• It is now possible to TOC and power off a vPar that is hung due to a defective PCI card driver.
• If the OA is restarted while iLO is unresponsive, the system no longer erroneously reports Power Redundancy Lost.
• Fixed an issue where iLO SSH may hang when OA uses SSH public keys for the auto login.

Bundle Version 2012.09

ENHANCEMENTS:

None

FIXES:

• Fixed an issue where a memory update operation may not complete properly when an L2 cache line encounters a second single bit data error. This may result in the possibility of undefined system behavior. See Intel Specification Update for more information. If Specification Update link does not work, HP recommend to go to www.intel.com  and search for the latest version of the Intel® Itanium® Processor 9300 Specification Update.
• Fixed an issue where PAL returned no information on bus log overflow
• Fixed an error where an uncorrected MCA with PSP that does not indicate an error type when PAL is catastrophic
• Fixed an issue on 8s system following OA reboot or takeover or PDHC restart which can result in Detached partitions.

 

Bundle Version 2012.02

ENHANCEMENTS:

None

FIXES:

• Fixed an issue to eliminate deconfiguration of healthy CPUs due to false cache errors (event 100819).

Bundle Version 2012.01

ENHANCEMENTS:

• Support for vPars v5 dynamic cores
• Dynamic core migration with Global Workload Manager(gWLM) and HP Instant Capacity (iCAP)
• Dynamic Processor Resiliency (DPR)
• Global Instant Capacity (GiCAP) grouping
• Locality Optimized Resource Alignment (LORA) for cores
• Support for rolling upgrades

FIXES:

• After an A/C power cycle or a complex “force” restart, the “SHOW TOPOLOGY” command or the GUI now correctly shows the second enclosure as part of the complex.
• After removing and putting back a blade into a slot, the DVD health LED no longer erroneously flashes yellow if the DVD is healthy.
• The command “show iox status” no longer displays the 'populated' and 'powered' fields which were invalid for IO.
• Syslog now shows proper error message at boot (CFW_EXCEED_LIMIT instead of “invalid output”) if the number of vPars to be activated exceeds the maximum number configured.
• The command “show oa info all” may no longer report the standby OA Firmware Bundle Revision as Unknown.
• vMedia applet now returns an error if “Launch Virtual media” is selected from the GUI while an existing applet window is already opened.
• When a firmware update is initiated from the OA via the UPDATE FIRMWARE command, existing OA GUI sessions are now disconnected or logged out.
• On a Superdome 2-8S server, the OA no longer reboots after issuing the command "parmodify -a" for adding a fifth blade to the nPartition.
• The ILM/SLM ratio is no longer changed to 100% (resulting in performance degradation) when the OA is rebooted after creating an nPartition in nPars mode without specifying an ILM/SLM value.
• An nPartition in MCA state will now auto power after A/C cycle or restart “force” complex.
• In nPars mode, the OA no longer restarts upon running a “reboot partition ” command on an nPartition
• The parstatus command no longer displays a status and run state “Active/MCA” after recovering from an LMCA (Local Machine Check Abort).
• Instant Capacity rc script startup failures are no longer reported during HP-UX boot as the Instant Capacity (iCAP) feature is now operational.
• The checkrevs command no longer reports mismatch warnings after OA switchover
• After running a “forced takeover” command from the OA CLI, 'show blade status' now shows a valid CPU type and populates the other CPU fields.
• Fixed an issue where some DIMM ECC errors were not reported
• Fixed an issue where deconfigured resources back to healthy state would remain unavailable (HR_DECONFIG_STATE_MISMATCH IPMI event logged)
• Reduced the possibility of the loss of OA network connectivity that can be caused by excessive OA network traffic
• Added a threshold for FMP reboots so that one time occurrences do not cause the assembly or assemblies to be falsely indicted

Complex Firmware Bundle Version 2.2.27

ENHANCEMENTS:

• Support for 32 socket complex (128 cores)
• Support for 8 IOXs for Superdome 2-16s and Superdome 2-32s
• Enablement of online firmware update and activation of complex firmware for future firmware releases.
• HP-SUM support for Customer Engineers
• 4TB memory
• Upgrades: Superdome 2-8s to Superdome 2-16s, Superdome 2-16s to Superdome 2-32s
• More I/O options: SAS I/O & Storage, Infiniband I/O cards, FCoE I/O cards
• Enablement of online firmware update of partition firmware (reboot of nPartition is require to activate).

FIXES:

• Fixed an issue where a good processor could be deactivated and de-configured due to excessive correctable L1 Instructions cache error (100821 event)
• Fixed an issue where a good processor could be deactivated and de-configured due to no spare directory cache lines (7010 event)
• SEGFAULT error reported when launching a CLI shell from the OA GUI using a user login other than the one that originally launched the CLI
• A partition can now successfully power on, even if one of its blades experiences a power-on failure
• Updated OA firmware to include the latest OA tray firmware
• Fixed an issue where the system might crash and reboot while attempting to update FPGA bits.
• Enhanced the “show xfm status all” command output to include full diagnostic status information
• The Insight Display “Health Summary" output now displays correctly after executing an OA force takeover
• OA USB connectivity status is now verified and cable status is reflected in the OA status output.
• Fixed an issue where a partition found in a transition state could be forced off upon an OA reboot
• Fixed an issue where DIMM address and parity errors were not correctly detected, causing the partition to crash, and error analysis showed a bad CPU or blade, when there was no actual hardware issue.
• Setting the Date time in the OA GUI using an NTP server now works.
• After recovering from a CAMNET connection failure, Parstatus no longer shows BLADE UNINTEGRATED/DEGRADED and 'show blade status' shows PDHC status OK.
• Fixed an issue where the DVD content could be seen even after the DVD drive was disconnected, or where the DVD content could not be seen after the DVD drive was reconnected.
• An XFM power fault no longer prevents the remaining XFMs from powering on, nor causes OA reboots or DL daemon death.
• Upon a nPar reboot in a server with 8 blades, SHOW SYSLOG OA no longer shows extra entries such as "Server Blade in bay 8 has been powered down" and "Server blade in bay 8 has been powered on".
• Improper error messages are shown for partition pages when a non-privileged user logs into the OA GUI.
• "show cae -L" output listing sequence is now in order even if the system time is changed
• Fixed an issue where some events could be dropped from the OA CLI DUMP command output.
• Prevent any user name that begins with a Superdome 2 reserved name from being added to the OA
• A partition may now boot successfully when an IOX is indicted or de-configured
• A LDAP user is now able to login into the OA CLI or GUI
• After a IOX indictment is cleared, the front panel health LED now goes back to green when health is restored to OK
• Fixed an issue where partitions may fail to power on when AC redundancy is enabled and no power is available from one power rail
• Fixed an issue where blade iLOs may become unresponsive.
• Fixed an issue where server would intermittently show the fan events FAN_STATUS_DEGRADED followed by FAN_STATUS_OK and an amber fan LED after an AC power cycle or a GPSM failover
• Show IOX status output no longer displays temperature for IOX Outlet Zone (not monitored)

Complex Firmware Bundle Version 1.3.0/1.3.1

ENHANCEMENTS:
None

FIXES:

• A firmware issue has been identified on HP Integrity Superdome 2 servers installed with firmware version 1.0.35 (initial release) or 1.2.67 (released 15 November 2010). Due to a polling timeout issue in the firmware, Superdome 2 servers running 99.4 days since the last firmware update or ‘AC power on’ can fail unexpectedly resulting in an unplanned outage of the entire system or a loss of partition management capability. This issue is resolved in firmware version 1.3.0.

Complex Firmware Bundle Version 1.2.67

ENHANCEMENTS:

• CPE Fixes and "Smart" offline Firmware Update -- improves firmware update when replacing spares with earlier revisions of firmware (outside of Manufacturing mode)

FIXES:

• Erroneous slot type information may be displayed in parstatus command verbose output
• Unable to assign some blade I/O to vPar with nPar powered on
• No alert is generated when a bulk power supply BPS_REMOVED or BPS_REDUNDANT event occurs.
• Boot options changes in EFI may be lost when followed by a partition reset and an AC power cycle occurred during the partition reset
• A system may crash after issuing a vPar memory addition command resulting in unaligned memory.
• Some vPars may hang during boot after the creation of new vPars if too many vPars have already been created.
• When the GUI is used to modify an active partition, clicking on the “Pending changes” TAB displays a page load error.
• When partition controller is down, partition related GUI pages may fail to load (page hangs with a loading screen).
• Momentary press button should be grayed out in the GUI for an nPar booted using EFI
• Partition power off/on button behavior is confusing while the partition is being powered off or on.
• During a virtual partition boot, the OA GUI does not display CPU information.
• Unable to use the vMedia applet after disconnecting a previously connected media.
• CFW error messages such as CFW_LOAD_ERROR_VPAR_DEF or CFW_EFI_VARIABLE_LOAD_FAILED may be generated during high activity.

INITIAL RELEASE:

Complex Firmware Bundle Version: 1.0.35

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@external.groups.hp.com?subject=FWupdateFeedback%20on%20SD2_2013.04