Exalogic Patch Set Update (PSU) Release 2.0.3.0.7 and 2.0.6.1.2 (Linux

Asset ID:	1-79-1684189.1
Update Date:	2015-02-25
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1684189.1 : Exalogic Patch Set Update (PSU) Release 2.0.3.0.7 and 2.0.6.1.2 (Linux - Physical) for July 2014

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.0.0.0 to 2.0.6.1.2
Exalogic Elastic Cloud X4-2 Hardware - Version X4 to X4 [Release X4]
Exalogic Elastic Cloud X3-2 Hardware - Version X3 to X3 [Release X3]
Oracle Exalogic Elastic Cloud X2-2 Hardware - Version X2 to X2 [Release X2]
Linux x86-64

Purpose

Oracle Exalogic is an integrated hardware and software system designed to provide a complete platform for a wide range of application types and widely varied workloads. It combines optimized Oracle Fusion Middleware software like WebLogic server, JRockit, Coherence with industry-standard Sun Server and Storage hardware and InfiniBand networking. The purpose of this document is to provide specific information around July 2014 Patch Set Update (PSU) for that system.

Scope

The target audience of this document are engineers and system administrators who plan to apply the Exalogic PSU.

This document provides the following:

README files that are included in the July 2014 PSU for convenience. These can be used for reference without having to download the PSU first
Errata - these include fixes to the README that were made after the PSU was released
Known issues with the PSU - these provide a list of known issues along with workarounds/solutions, if available. Engineers and administrators planning to apply the PSU should ensure to review these before applying the PSU

This document will be kept up-to-date with updates to errata and known issues.

Details

Patch Download

Released: July 2014

Product Version: 2.0.3.0.7 (on X2-2/X3-2), 2.0.6.1.2 (on X4-2) for Oracle Linux x86-64

PATCH:18630746- EXALOGIC LINUX 2.0.4.0.7 2.0.3.0.7 (on X2-2/X3-2), 2.0.6.1.2 (on X4-2) PATCH SET UPDATE (PSU) FOR JULY 2014

IMPORTANT NOTE

Before applying the above July 2014 patch (i.e 18630746), following patch 19323699 should be applied to the downloaded July 2014 PSU bits.

PATCH:19323699 - ONE-OFF PATCH TO JULY 2014 PSU BITS FOR EL PHYS LINUX WITH FIX FOR BUG

Patch 19323699 installation instructions are in the README file in p19253153_20300_Linux-x86-64.zip.

Applying this patch 19323699 to the July 2014 PSU BITS for Exalogic Physical Linux prevents the following bug from being encountered following the application of the PSU:

BUG 19253153 - VNIC'S DOWN AFTER LINUX PHYSICAL JULY 2014 PSU UPGRADE 2.0.3.0.7

Patch Readme Documentation

Refer to the the readme documentation attached 18630746-Linux.zip to this Document on how to upgrade the Exalogic infrastructure:

Exalogic X2-2 and X3-2 Systems: Upgrading to 2.0.3.0.7
Exalogic X4-2 Systems: Upgrading to 2.0.6.1.2

The readme content structure layout of the 18630746-Linux.zip:

Appendices

Appendix A: Readme Documentation Errata

July 2014 PSU for EL Physical Linux

Errata

C-State needs to be DISABLED on the compute nodes

Original Text

In section 1.1 entitled “Preparing to Apply Base Image Updates to Compute Nodes”, step 2d under “Modify BIOS Settings” contains the following text:

In the Cpu Configuration screen, ensure that Intel(R) C-State tech is set to Enabled.

Updated Text

C-State needs to be DISABLED on all compute nodes. The updated text should read as follows:

In the Cpu Configuration screen, ensure that Intel(R) C-State tech is set to Disabled.

The Oracle ZFS Storage appliance on X4-2 racks is incorrectly referred to as ZFS Storage 7320 in the PSU. The storage appliance on Exalogic X4-2 racks is Oracle ZFS Storage ZS3-ES.

Appendix B: Fixed Bugs List

Please review Document ID : 1905523.1 - Exalogic Infrastructure July 2014 PSU - Fixed Bugs List.

Appendix C: Patching Known Issues

Upgrading NM2 Switch Firmware on full rack Exalogic systems or multi-rack Exa systems causing Network outage

Note:

The issue does not occur when Exalogic racks (one eighth, quarter, half ) are connected to Exadata racks.

Symptoms

Network outages on the InfiniBand fiber.

Cause

The NM2 Port ID space has increased four times from firmware version 2.0 to to 2.1. Therefore, port ID collisions may occur if NM2 switches with firmware version 2.0 and 2.1 are run on the same fabric. This issue can cause network outages on the InfiniBand fiber.

Solution/Workaround

In order to prevent this issue, manipulation of the switch 'GWInstance' value may be required to ensure unique port IDs are generated by performing the following steps:

Log in to each NM2-GW switch as root and run:

# showgwconfig

Note the GWInstance "Running Value" on each of the switches.

1. Ensure that all the GWInstance values are even numbers
2. Ensure that GWInstance values when multiplied by 4, are greater than the largest GWInstance value.

To change a GWInstance value to 16, run:

[root@nm2gw-ib01 ~]# setgwinstance 16
Stopping Bridge Manager.. [ OK ]
Starting Bridge Manager. [ OK ]
root@nm2gw-ib01 ~]#

For example, if the GWInstance values of four NM2 switches are 10, 20, 30 & 40, it will be necessary to change the GWInstance value of 10 to 16.

Applying July 2014 PSU causes EoIB Network on node to become unavailable

Symptoms

After applying the July 2014 PSU to compute nodes, any EoIB network interfaces may become unavailable. The compute node is unable to ping the router on the EoIB network. If NIS is configured on the EoIB network, login takes an abnormally long time due to NIS being unavailable.

Cause

The EoIB network interfaces are mis-configured by the July 2014 due to the following bug:

BUG 19253153 - VNIC'S DOWN AFTER LINUX PHYSICAL JULY 2014 PSU UPGRADE 2.0.3.0.7

The MTU is incorrectly configured to be 65520 for EoIB (not IPoIB) networks.

Solution/Workaround

Edit the interface configuration file(s) for EoIB network interfaces on all patched compute nodes. For instance, if bond1 corresponds to an EoIB network, perform the following steps:

1. As user root, change directory to /etc/sysconfig/network-scripts

2. In this directory, edit the ifcfg file corresponding to the EoIB network interface (ifcfg-bond1 in this example)

3. Comment out the following lines:

MTU=65520
CONNECTED_MODE=yes

4. Save the file

5. Repeat for all EoIB network interfaces (not IPoIB interfaces) configured on the node.

6. Perform the same change for the eth0 interface, since that interface is also mis-configured by the PSU.

a. Edit ifcfg-eth0 and comment out the same two lines.

7. Reboot the compute node

8. Repeat for all patched compute nodes

Alternatively, you can download and apply the following patch to your compute nodes which will automatically apply the above workaround:

PATCH:19253153 - VNIC'S DOWN AFTER LINUX PHYSICAL JULY 2014 PSU UPGRADE 2.0.3.0.7

Patching of X2-2/X3-2 Exalogic Compute Node from version 2.0.3.0.6 does not enable updated disk controller

Symptoms

After applying the July 2014 PSU to compute node X2-2/X3-2 which were originally at image version 2.0.3.0.6, /opt/exalogic.tools/tools/CheckHWnFWProfile fails with "Disk controller is not at the supported firmware version. It requires firmware update..."

portion of the o/p:

Supported disk controller Version: 12.12.0-0178
Current disk controller Version : 12.12.0-0079
Disk controller is not at the supported firmware version. It requires firmware update...
Supported disk controller Firmware at: /opt/exalogic/firmware/disk_controller/12_12_0_0178.rom

Does not contain required firmware
bios : 1
ilom : 1
ibfw : 1
dcfw : 0

Cause

The PSU has upgraded the newer disk controller v12.12.0-0178, but it is not yet enabled.

Solution/Workaround

After the patching is complete, manually reboot the compute node. Re-login to the compute node and re-run /opt/exalogic.tools/tools/CheckHWnFWProfile to confirm it passes without any errors.

Post Reboot, nodes patched from v2.0.0.0.x do not have expected exalogic-java-1.1-6.noarch.rpm, infinibus-1.1-225.x86_64.rpm

Symptoms

After patching nodes starting at 2.0.0.0.x, the CheckSWProfile fails after a reboot:-

[root@compute-node tools]# ./CheckSWProfile
[SUCCESS]........Has supported operating system
[SUCCESS]........Has supported processor
[SUCCESS]........Kernel is at the supported version
[SUCCESS]........Has supported kernel architecture
[FAILURE]........Software does not match with the supported profile. See below.
[FAILURE]........Not found: exalogic-java-1.1-6.noarch.rpm, infinibus-1.1-225.x86_64.rpm

Cause

This happens due to known unpublished Bug 20506674 during upgrade. Each time the node reboots, a initialization script runs and performs action based on /etc/sysconfig/init-exalogic-node params. In versions starting at v2.0.0.0.x, the ebi_post_patch.sh incorrectly writes initialization flag INSTALL_REQUIRED_PACKAGES=YES into the /etc/sysconfig/init-exalogic-node file. And so upon reboot, the infinibus and exalogic-java are reinstalled with default lower version that came with exalogic-2.0.3.0.0-1.0.noarch.rpm:- exalogic-java-1.1-5 and infinibus-1.0-69.

Solution/Workaround

In the patched node, make sure all params in init-exalogic-node are set to "NO" immediately after the patching is complete. i.e., Check /etc/sysconfig/init-exalogic-node:-

RUN_NODE_INITIALIZATION=NO

RUN_NETWORK_UPDATE=NO

INSTALL_REQUIRED_PACKAGES=NO

INSTALL_REQUIRED_PACKAGES_FAILED=NO

Note that above issue is only when the starting version is v2.0.0.0.x.

References

<NOTE:1449226.1> - Exachk Health-Check Tool for Exalogic
<NOTE:1314535.1> - Exalogic Patch Set Updates (PSU) Master Note
<NOTE:1329262.1> - How to Perform a Healthcheck on Exalogic
<BUG:20506674> - REBOOT FOLLOWING EXALOGIC PSU PATCHING DOWNGRADES EXALOGIC-JAVA AND INFINIBUS

Attachments

This solution has no attachment