Oracle Exalytics Release 2.0.0.0.0 and 2.0.0.1.0 Known Issues After Patchset (PS) Install

Asset ID:	1-79-2247786.1
Update Date:	2017-05-09
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 2247786.1 : Oracle Exalytics Release 2.0.0.0.0 and 2.0.0.1.0 Known Issues After Patchset (PS) Install

Applies to:

Exalytics In-Memory Machine X2-4 - Version All Versions and later
Exalytics In-Memory Machine X5-4 - Version All Versions and later
Exalytics In-Memory Machine X6-4 - Version All Versions and later
Oracle Exalytics Software - Version 2.0.0.0.0 and later
Exalytics In-Memory Machine X3-4 - Version All Versions and later
Linux x86-64

Purpose

This document provides detailed information on known installation issues for Oracle Exalytics Patchsets on Release 2.0.0.0.0 and 2.0.0.1.0. Affected Patchset (PS) releases are indicated.

Scope

This document is intended for systems administrators or network specialists who may be involved in configuring or patching the Exalytics server. Installation of these patches is accomplished by following the steps in the patch readme files and the Installation and Administration Guide for Oracle Exalytics In-Memory Machine. This document includes issues that may be encountered while patching an Exalytics server.

Details

The Exalytics release notes describe known issues and workarounds and should always be checked before doing any new installs or patchset installs. Release notes for each Exalytics release are available on the Exalytics documentation index. The items listed below are known issues that were found after applying Exalytics Patchsets on an Oracle Exalytics server and that may not be included in the release notes. Affected Releases/Patchset (PS) versions are indicated.

BASE IMAGE / IMAGE VERSION

Inconsistent and Unexpected Linux Kernel Versions When Running /opt/exalytics/bin/exalytics_imageinfo Command

Symptoms: After applying Exalytics Release 2.0.0.0 on an existing bare metal PatchSet (PS) 5 machine, the exalytics_imageinfo command does not show the same kernel version in all locations. Specifically:

# /opt/exalytics/bin/exalytics_imageinfo
Image version : 2.0.0.0_el5
Creation timestamp : Fri 29 May 2015 03:16:55 PM EDT
Kernel version : 2.6.39-400.248.3.el5uek ] --- shows -400.248.3. ---

RPM versions:
kernel-uek-2.6.39-400.248.3.el5uek ] --- kernel version here matches above version ---
kernel-2.6.32-100.23.1.el5 ] --- shows lower level kernel version ---
exalytics-container-bm-2.0.0.0-2_el5
exalytics-scripts-2.0.0.0-9_el5
exalytics-flash-2.0.0.0-2_el5
exalytics-domain-configure-2.0.0.0-4_el5
exalytics-deps-exact-2.0.0.0-2_el5
exalytics-deps-minimum-2.0.0.0-2_el5

Kernel version shows as 2.6.39-400.248.3.el5uek but the 'kernel' listed under the RPM versions shows kernel-2.6.32-100.23.1.el5.

Affected Releases: Exalytics Release 2.0.0.0.0

Bug Number: <Bug 21665671> - EXALYTICS:UNEXPECTED RPM KERNEL VERSION AFTER REL 2.0.0.0 INSTALL ON PS5 BM

Cause: This is expected behavior. Per Exalytics Development in the above bug and in the Install Guide, the Kernel Version displayed just below the "Creation timestamp," (line 3 above) is the actual updated kernel version. The RPM kernel version (2nd number in the RPM list - kernel-2.6.32-100.23.1.el5) indicates the patch build number. Build number can vary and this is not cause for concern. If line 3 does not show (2.6.39-400.248.3.el5uek), then the patch may not have been applied correctly and may need to be re-installed.

Solution: No Action Required as long as kernel version shows 2.6.39-400.248.3.el5uek. If kernel version (after release 2.0.0.0.0 install) does not show 2.6.39-400.248.3.el5uek, then re-apply the patch.

HARDWARE/MANAGEMENT

ASR Missing from Linux 6 After Install or Re-Image

Symptoms: After installing Linux 6, or re-imaging a Linux 5 server to Linux 6 and Release 2.0.0.0.0 or 2.0.0.1.0, Auto Service Request (ASR) is missing and not found on the server.

Affected Releases: Exalytics releases 2.0.0.0.0 and 2.0.0.1.0

Bug Number(s): Internal, unpublished bugs:

<Bug 21565893> - ASR DOES NOT WORK IN EXALYTICS RELEASE2(LINUX6.6)
<Bug 21645584> ASR SCRIPTS USE INCORRECT PATH TO IPMITOOL IN 2.0.0.0EL6 IMAGE
<Bug 24473221> DOC: UPDATE OWNERS GUIDE FOR ASR MANAGER SOFTWARE AND LINUX 6

Cause: ASR Utility inadvertently omitted from base image updates.

Solution: Download and install <Patch 21645584> ASR SCRIPTS USE INCORRECT PATH TO IPMITOOL IN 2.0.0.0EL6 IMAGE and <Patch 21565893> ASR DOES NOT WORK IN EXALYTICS RELEASE2(LINUX6.6) as described in the readme.txt files and in Exalytics - Auto Service Request (ASR) Utility Missing from Base Image in Release 2.0.0.0.0 and 2.0.0.1.0 <Document 2180975.1>.

ILOM Remote Console Fails - "No Appropriate Protocol (protocol is disabled or cipher suites is inappropriate)"

Symptoms: ILOM remote console fails to launch properly. Problem may vary depending on browser type. Internet Explorer (IE) browser fails with error "No appropriate protocol (protocol is disabled or cipher suites are inappropriate)" while Firefox fails to start the console and repeatedly prompts user to open "jnlpgenerator-16" files over and over. This issue may occur even if the ILOM remote console was previously used successfully on the same client machine.

Affected Releases: All Exalytics releases; java specific (JDK 8u31, JDK 7u75, JDK 6u91 and later)

Bug Number(s): N/A - change in java product

Cause: Changes in java security settings. This issue occurs with January 20, 2015 Critical Patch Update releases (JDK 8u31, JDK 7u75, JDK 6u91 and later), because in these releases the Java Runtime Environment has SSLv3 disabled by default. Specific versions of ILOM Remote System Console use SSLv3 sockets to connect to the SP.

Solution: Complete the following steps to allow successful launch of ILOM remote console:

1. Ensure the current firmware patches are installed on the Exalytics server - see Installation guide for your installed version.

2. On any client machine used to access the ILOM remote console, locate file $JAVA_HOME/jre/lib/security/java.security and comment out the line that reads:

jdk.tls.disabledAlgorithms=SSLv3

The modified file should show:

# jdk.tls.disabledAlgorithms=SSLv3

NOTE: You may have multiple versions of java installed on the client machine (i.e. Java 7 and Java 8). If so, you need to comment out the "SSLv3" entry on the java.security file in each java home, i.e. C:\Program Files\Java\jre1.7.0_71\lib\security; C:\Program Files (x86)\Java\jre1.8.0_31\lib\security; etc..

Windows PC users must have Administration rights on the client machine to make changes to a java.security file. If you do not have Admin rights to the PC, select Start -> Accessories -> right click on Wordpad and select "run as administrator".
When Wordpad application starts, click Open and navigate to the the java.security file. When you save file, be sure to save as a java.security file and not a Wordpad application file type.

3. After making changes, restart web browser and re-attempt connection to ILOM remote console.

NOTE: If Firefox browser again prompts for action to take on "jnlpgenerator-16" file, select browse -> then search in the $JAVA_HOME/bin directory and locate "javaws.exe" in the program files\java\bin directory. Be sure to set the option to "Do this automatically for files like this from now on." If you do not select the option, your changes will not be persistent for any subsequent browser sessions.

NETWORK

Infiniband Diagnostics Tools Commands "ibhosts" and "ibswitches" Fail with Errors

Symptoms: After release 2.0.0.1.0 install, the infiniband diagnostics tools commands "ibhosts" and "ibswitches" fail with errors:

src/query_smp.c:228; can't open UMAD port ((null):0)
/usr/sbin/ibnetdiscover: iberror: failed: discover failed

Affected Releases: Release 2.0.0.1.0

Bug Number: Internal, unpublished <Bug 24750720> - IB DIAGNOSTIC TOOLS DOES NOT WORK WITH R2.1 INSTALLATION AND UPGRADE

Cause: The diagnostics tools were inadvertently omitted from the Release 2.0.0.1.0 software. Exalytics Development determined that the error does not prevent infiniband connections from being made, but it prevents use of the diagnostic tools to check status and connections on infiniband.

Solution: Download <Patch 24750720> IB DIAGNOSTIC TOOLS DOES NOT WORK WITH R2.1 INSTALLATION AND UPGRADE. Install the patch as described in the patch readme.txt file. After patch installation, the IB diagnostics tools command will run without error.

ORACLE VIRTUAL MACHINE (OVM) ON EXALYTICS

Errors on OVM 3.3.3 Reboot "firmware has been previously dumped ... reverting to slow read"

Symptoms: After installing OVM 3.3.3 via Patch 22546910 and rebooting server, firmware and slow read errors are reported:

qla2xxx [0000:a0.0]-d00d:7 firmware has been previously dumped (ffffc90018781000) -- ignoring request
qla2xxx [ 000:a0:0001]-00f5:7 unable to burst-read optrom segment (100/758fc400/80f94dc000)
qla2xxx [000:a0:00:0]-00f6:7 Reverting to slow read

Affected Releases: Exalytics releases 2.0.0.0.0 and 2.0.0.1.0 with OVM 3.3.3

Bug Number(s): Internal unpublished bugs: <BUG 22341180> - GET QLA2XXX ERROR AFTER APPLYING OVM 3.3.3 AND KERNEL-UEK-3.8.13-98.5.2.EL6UEK and <BUG 20745556> - ISSUE WITH LACP BOND MODE WITH 1 GB NIC WITH DOM0_MAX_VCPUS=20.

Cause: This issue occurs due to known product defects in the XEN package on OVM server 3.3.3.

Solution: Bug will be fixed in OVM 3.3.4 which is currently not available for Exalytics.

Workaround:

Login to system as root user and make a backup copy of the /boot/grub/grub.conf file.
Then use vi to edit the file and and modify the setting for "dom0_max_vcpus". Set this to be 8.
Save changes to the grub.conf file and reboot the server.
Once the server is rebooted again, it will start up correctly.

No controllers found when Running flash configuration command "ddcli" Command on X5-4 Server with OVM 3.3.3

Symptoms: Followed Release 2.0.0.0.0 Exalytics Installation Guide steps to install OVM 3.3.3 on a new X5-4 server. When running the ddcli command to configure flash, the following messages are seen:

# ddcli

****************************************************************************
LSI Corporation WarpDrive Management Utility
Version 107.00.00.04 (2012.06.05)
Copyright (c) 2011 LSI Corporation. All Rights Reserved.
****************************************************************************

LSI WarpDrive Management Utility: No controllers found.

Affected Releases: Exalytics Release 2.0.0.0.0 with OVM 3.3.3

Bug Number(s): <BUG 21855641> - FLASH DRIVES NOT SEEN ON X5-4 DOM0 EVEN AFTER APPLYING THE PATCH 21258871 and internal unpublished bugs <BUG 21918984> - EXALYTICS X5-4 REQUIRES A SUPPORTED VIRTUAL IMAGE FOR INSTALLATIONS and <BUG 22618897> - EXALYTICS R2: NEED TO PRESENT THE FLASH CARDS TO OVM TO ASSIGN TO EXALYTICS.

Cause: Base image and documentation errata. Unlike other Exalytics X series servers, X5-4 (and X6-4) servers use nvme flash cards. The ddcli command is not the correct command to use to check the nvme flash configuration. Instead of 'ddcli' command, it should be 'nvmeadm list' on an X5-4 or X6-4 server.

Solution: Apply <Patch 22546910> and complete the steps in the Patch readme. Then run the "nvmeadm list" command to verify the flash (in lieu of ddcli command).

Example:

# nvmeadm list
SUNW-NVME-1
SUNW-NVME-2
SUNW-NVME-3

"Error: starting sector number, 4687499264 exceeds the msdos-partition-table-imposed maximum of 4294967295" When Configuring RAID1 for Flash on OVM

Symptoms: Running "parted -a optimal /dev/nvme0n1 mkpart primary 0% 25% mkpart primary 25% 50% mkpart primary 50% 75% mkpart primary 75% 100%" command to configure RAID1 for flash on OVM fails to create all partitions and reports error:

Error: starting sector number, 4687499264 exceeds the msdos-partition-table-imposed maximum of 4294967295

Reference step 2, under Section 3.7.3 Configuring RAID1 for Flash in Oracle VM Server on X5-4 and X6-4 Machines in the Exalytics Installation Guide

Affected Releases: Exalytics Release 2.0.0.1.0, X5-4 and X6-4 Models

Bug Number: Unpublished <BUG 25611437>, ISSUE RELATED TO EXALYTICS X6-4 3200GB NVME CARDS.

Cause: Documentation bug

Solution: Modify step 1 under Section 3.7.3 Configuring RAID1 for Flash in Oracle VM Server on X5-4 and X6-4 Machines in the Exalytics Installation Guide. Instead of running the command in Step 1 as: "#parted /dev/nvme0n1 mklabel msdos" run command as:

#parted /dev/nvme0n1 mklabel gpt

Note: This command will wipe out any existing partitions. Accordingly, if there are existing partitions on the server, you need to back them up before running this command. No other changes are required - continue with remaining steps under Section 3.7.3.

OVM Manager 3.3 Web Console "ERR_SSL_VERSION_OR_CIPHER_MISMATCH"

Symptoms: Launching OVM Manager 3.3.3 web console fails with browser error "ERR_SSL_VERSION_OR_CIPHER_MISMATCH." Problem known to occur with Chrome and Firefox web browsers.

Bug Number: Internal, unpublished <BUG 22584886> - OVM: ERR_SSL_VERSION_OR_CIPHER_MISMATCH WITH CHROME 48

Solution: Bug will be fixed in OVM Manager 3.3.4 which is currently not supported with Exalytics.

Workaround: Complete these steps as a workaround:

1. Make a backup of the Weblogic config file

# cd /u01/app/oracle/ovm-manager-3/domains/ovm_domain/config
# cp config.xml config.xml.bak

2 Edit the file config.xml, and add a line <ciphersuite>TLS_RSA_WITH_AES_128_CBC_SHA</ciphersuite>

It should looks like:

<ssl>
<name>AdminServer</name>
<enabled>true</enabled>
<ciphersuite>TLS_RSA_WITH_RC4_128_SHA</ciphersuite>
<ciphersuite>TLS_RSA_WITH_RC4_128_MD5</ciphersuite>
<ciphersuite>TLS_RSA_WITH_AES_128_CBC_SHA</ciphersuite>
<hostname-verifier>weblogic.security.utils.SSLWLSWildcardHostnameVerifier</hostname-verifier>

3 Restart the ovmm service:

# service ovmm restart

References

<NOTE:2046791.1> - Exalytics: After Release 2.0.0.0 Upgrade on Bare Metal PS5 Server "exalytics_imageinfo" Command Shows Non-Matching Kernel Versions under "kernel" and "RPM"
<NOTE:2163123.1> - Exalytics: Cannot See Flash Disk with "ddcli" Command after Installing OVM 3.3.3 on an X5-4 Server
<NOTE:2243754.1> - Configuring NVME Cards on Exalytics X6-4 Fails with Error: “Error: starting sector number, 4687499264 exceeds the msdos-partition-table-imposed maximum of 4294967295”
<NOTE:1987885.1> - Oracle Exalytics: ILOM Remote Console Fails to Start or Starts and Reports Error: "No Appropriate Protocol (protocol is disabled or cipher suites is inappropriate)"
<NOTE:2243505.1> - Exalytics Release 2.0.0.1 Infiniband Diagnostics Tools Commands "ibhosts" and "ibswitches" Return Error: ".../usr/sbin/ibnetdiscover: iberror: failed: discover failed"
<NOTE:2105497.1> - Reboot of Exalytics X5-4 Server after Release 2.0.0.0.0 Upgrade shows Errors: "qla2xxx [0000:a0.0]-d00d:7 firmware has been previously dumped...Reverting to slow read"
<NOTE:2099148.1> - Oracle VM Manager 3.3: getting error ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Chrome

Attachments

This solution has no attachment