ODA: Version 1 (V1) Fails to Apply the Core Key Due to an Invalid Serial Number : Command "oakcli apply core_config

Asset ID:	1-72-1503174.1
Update Date:	2015-12-15
Keywords:

Solution Type Problem Resolution Sure

Solution 1503174.1 : ODA: Version 1 (V1) Fails to Apply the Core Key Due to an Invalid Serial Number : Command "oakcli apply core_config_key" Failure

Applies to:

Oracle Database Appliance Software - Version 2.3.0.0 to 2.4.0.0 [Release 2.3 to 2.4]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
While there can be several reasons for the Serial Number messages on the ODA Bug 14206882 - OAKVALIDATE ERROR: INVALID SYSTEM SERIAL NUMBER AFTER PATCH TO 2.3 only applies to ODA Hardware Version V1. The reason is that V1 is the ONLY ODA hardware version which goes back as far as 2.3. The release of the X3-2 ( ODA V2) started no earlier than 2.4 but was most commonly known as being 2.5 and higher. No ODA Patches from 2.3 or earlier can be applied on any of the newer ODA HW versions

Symptoms

Requires OAK version 2.3.0.0.0 and ODA Hardware Version V1 ( SUN FIRE X4370 M2 SERVER )

To confirm if using the V1 ODA issue the following as root

# fwupdate list sp_bios

Example

[root@odax ~]# fwupdate list sp_bios
==================================================
SP + BIOS
==================================================
ID Product Name ILOM Version BIOS/OBP Version XML Support
-------------------------------------------------------------------
sp_bios SUN FIRE X4370 M2 SERVER v3.0.16.22.f r100119 12010311 N/A

Symptoms

1. oakcli apply core_config_key fails with : Failed to set core count due to invalid serial number

-OR-

2. oakcli validate -c SystemComponents fails with 'Error: Invalid System Serial number'

Trying to fetch the serial number (which oakcli also uses internally to obtain the serial number) -- Only valid for the ODA V1 X4370 M2

[root@oak1 ~]# /usr/sbin/dmidecode -t1 |grep Serial

Serial Number: Not Available

Changes

Applied OAK version 2.3.0.0.0

-OR-

New ODA deployment with 2.3.0.0.0

Cause

Unpublished Bug 14206882 - OAKVALIDATE ERROR: INVALID SYSTEM SERIAL NUMBER AFTER PATCH TO 2.3

Solution

Workaround:

Reset the ILOM on both nodes and reboot the machine.

A permanent Solution is to apply OAK version 2.4.0.0.0

- OAK 2.4.0.0.0 includes ILOM version 3.0.16.22.a-r75629, which has a permanent fix for the bug.

For ODA Core Key problems on newer hardware and ODA versions please refer to:

1638577.1 - ODA Troubleshooting ODA Core Key Generation and Application Problems

References

<BUG:14206882> - LNX64-112-CMT: OAKVALIDATE ERROR: INVALID SYSTEM SERIAL NUMBER AFTER PATCHTO 2.3
<NOTE:1447093.1> - Oracle Database Appliance - Steps to Generate a Key via MOS to change your CORE Count and apply this Core Key
<NOTE:1638577.1> - ODA Troubleshooting ODA Core Key Generation and Application Problems

Attachments

This solution has no attachment