ODA ODAVP "oakcli apply core_config_key" Fails with "ERROR: Invalid Serial number, cannot set the core count"

Asset ID:	1-72-2035218.1
Update Date:	2018-02-20
Keywords:

Solution Type Problem Resolution Sure

Solution 2035218.1 : ODA ODAVP "oakcli apply core_config_key" Fails with "ERROR: Invalid Serial number, cannot set the core count"

Applies to:

Oracle Database Appliance X4-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X5-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
ODA,oakcli, core_key,

Symptoms

Primary Symptom : Unable to apply a Core Key on an Oracle Database Appliance on any version with messages : "...Invalid Serial number..."

Other reasons for Core Key application failure are discussed in Document: 1638577.1 - ODA Troubleshooting ODA Core Key Generation and Application Problems

Example:

[root@oda1]oakcli apply core_config_key /key_file_location/core_key_filename

"ERROR: Invalid Serial number, cannot set the core count"

Changes

Attempting to apply a Core Key on the Oracle Database Appliance (ODA) including V1, X3-2, X4-2 and X5-2.
This note is not designed to troubleshoot X6-2 ODA but may still provide some suggestions when troubleshooting the problem on X6-2 lite and HA versions

While this problem is most likely to occur during the first attempt to apply a Core Key, this problem can technically appear any time a new core key is being applied.

One source not discussed is regarding failure to copy the key properly or cleanly from MOS.
- We always recommend checking the byte size of the key from source and thru copying to the ODA ( common sizes are 176 and 180 bytes )

Cause

One reason the ODA Core Key application can fail is when the SYSTEM_IDENTIFIER information is missing or incorrect on one or both nodes.
Comment:
Incorrect System_Identifier information is usually due to either re-imaging and wiping the ILOM or MANUAL intervention of information in the ILOM.

The SYSTEM_IDENTIFIER is a text string that must pass exact format specifications or you can see the "...Invalid Serial number..." message during Core Key application.

Each Node's SYSTEM SYSTEM_IDENTIFIER can be manually or accidentally altered in the ILOM or by command line resulting in validations failing during the Core Key application procedure.
If is important to review the SYSTEM_IDENTIFIER if you have ruled out all other sources for the problem as discussed in Note 1638577.1.
The proper format for the SYSTEM_IDENTIFIER is based on the following information and must exactly match the format including spaces.

The FORMAT for the System identifier is PRODUCT + HW PLATFORM + SERIAL#

X3-2 /X4-2/X5-2 system_identifier = Oracle Database Appliance X4-2 1234NMP012 -- example for X4-2

For V1 there is NO reference to the HW Platform/tyoe

Just use PRODUCT + SERIAL#

V1 system_identifier = Oracle Database Appliance 1234NMP023 -- example for V1

Case 1

Node0 incorrect -- Missing HW platform reference and Serial Number
Node1 incorrect -- (none) MISSING all three
Node Mismatch -- Information not the same for both nodes

Excerpt from

ipmitool sunoem cli "show /System"

...
  Properties:
  check_physical_presence = true
  current_hostname = oda03-ilom
  hostname = oda03-ilom
  reset_to_defaults = none
  system_contact = (none)
  system_description = SUN SERVER X4-2, ILOM v3.2.4.20.a, r94217
  system_identifier = Oracle Database Appliance <<<<<<<<<<<<<<<<< MISSING HW platform X4-2 and Serial Number
  system_location = (none)
...

Properties:
  check_physical_presence = true
  current_hostname = oda04-ilom
  hostname = oda04-ilom
  reset_to_defaults = none
  system_contact = (none)
  system_description = SUN SERVER X4-2, ILOM v3.2.4.20.a, r94217
  system_identifier = (none) <<<<<<<<<<<<<<<<< MISSING all three -- PRODUCT + HW PLATFORM + SERIAL#
  system_location = (none)
...

Case 2

Node0 incorrect -- Missing correct HW platform
Node1 incorrect -- Missing everything (none)
Node Mismatch -- Information not the same for both nodes

system_identifier = Oracle Database Appliance 1234NMP023 << This might be correct for the original ODA V1 , but will not be correct for X3-2, X4-2 or X5-2 as there is no reference to the HW Platform

Excerpt from ipmitool sunoem cli "show /System"

First Node
...
current_hostname = oda01-ilom
  hostname = oda01-ilom
  reset_to_defaults = none
  system_contact = (none)
  system_description = SUN SERVER X4-2, ILOM v3.2.4.20.a, r94217
  system_identifier = Oracle Database Appliance 1414NMP016                    <<<<<<<< Missing Hardware Platform X4-2
  system_location = (none)
...

Second node
...
current_hostname = oda02-ilom
  hostname = hc1pl- oda02-ilom
  reset_to_defaults = none
  system_contact = (none)
  system_description = SUN SERVER X4-2, ILOM v3.2.4.20.a, r94217
  system_identifier = (none)          <<<<<<<<<<<<<<<<< MISSING all three: PRODUCT + HW PLATFORM + SERIAL#

...

Solution

The Serial Number for X3-2 X4-2 and X5-2 should be identical on both nodes for both of the following

# ipmitool sunoem getval /X/system_identifier

Target Value: Oracle Database Appliance X5-2 12345...........

# oakcli show server

        Power State            : On
        Open Problems            : 0
        Model                      : ODA X.........
        Type                    : Rack Mount
        Part Number              : 333.......
        Serial Number            : 12345.... <<<<<<<<<
        Primary OS               : Not Available
        ILOM Address               : 10........
        ILOM MAC Address         : 00:...............
        Description                     : Oracle Database Appliance X5-2 12345..... <<<<<<<<   X3-2 or X4-2 depending on the HW-Type
        Locator Light           : Off
        Actual Power Consumption : 360 watts
        Ambient Temperature      : 24.000 degree C
        Open Problems Report     : System is healthy

Review the existing system_identifier values using ipmitool on each node

Replace missing or incorrect values

root@oda1 ~]# ipmitool -I open sunoem getval /X/system_identifier

If it is not correct: Set the proper value

ipmitool -I open sunoem setval /X/system_identifier "<product_name> <HW Platform> <system_serial_number>"

Example

[root@oda ~]# ipmitool -I open sunoem setval /X/system_identifier "Oracle Database Appliance X4-2 1234NMP567P"
Sun OEM setval command successful.

NOTE             For the Product and HW version use the following table

for X3-2    Oracle Database Appliance X3-2 <system_serial_number>
for X4-2    Oracle Database Appliance X4-2 <system_serial_number>
for X5-2          Oracle Database Appliance X5-2 <system_serial_number>

for V1 use Oracle Database Appliance <node_serial_number> -- no reference to the HW as this was the first HW version

Example

PRODUCT: Oracle Database Appliance
HW PLATFORM: X4-2
SERIAL#: 1234NMP012

system_identifier = Oracle Database Appliance X4-2 1234NMP012

Correct Excerpt from ipmitool sunoem cli "show /System"

First Node

Properties:
  check_physical_presence = true
  current_hostname = oda01-ilom
  hostname = oda01-ilom
  reset_to_defaults = none
  system_contact = (none)
  system_description = SUN SERVER X4-2, ILOM v3.2.4.20.a, r94217
  system_identifier = Oracle Database Appliance X4-2 1234NMP012 <<<<<<< Complete PRODUCT + HW PLATFORM + SERIAL#
  system_location = (none)

Second Node

Properties:
  check_physical_presence = true
  current_hostname = oda02-ilom
  hostname = oda02-ilom
  reset_to_defaults = none
  system_contact = (none)
  system_description = SUN SERVER X4-2, ILOM v3.2.4.20.a, r94217
  system_identifier = Oracle Database Appliance X4-2 1234NMP012 <<<<<<<<<< Complete PRODUCT + HW PLATFORM + SERIAL#
  system_location = (none)

SUPPORT collect ILOM for both nodes of the ODA

-> show /SP
-> show /System

-> set SESSION mode=restricted
[(restricted_shell) sp:~]$ showpsnc

[(restricted_shell) sp:~]$ exit

References

<BUG:20732508> - LNX64-121-CMT: SYSTEM_IDENTIFIER SHOULD BE NON-MODIFIABLE OR PROTECTED
<BUG:21417720> - ODA CORE KEY NOT APPLYING ON RE-IMAGED X4-2 12.1.2.3.0 SYSTEM_IDENTIFIER PROB
<NOTE:1638577.1> - ODA Troubleshooting ODA Core Key Generation and Application Problems
<NOTE:1447093.1> - Oracle Database Appliance - Steps to Generate a Key via MOS to change your CORE Count and apply this Core Key
<NOTE:1597084.1> - ODA FAQ : Understanding the Oracle Database Appliance Core Key Generation usage, common questions and problems ( FAQ )

Attachments

This solution has no attachment