Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2095097.1
Update Date:2016-01-13
Keywords:

Solution Type  Technical Instruction Sure

Solution  2095097.1 :   ODA How To Identify the Serial Number for the Oracle Database Appliance  


Related Items
  • Oracle Database Appliance X4-2
  •  
  • Oracle Database Appliance
  •  
  • Oracle Database Appliance X5-2
  •  
  • Oracle Database Appliance X3-2
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
  •  


Finding and registering the correct serial numbers on the two Oracle Database Appliance (ODA) servers is critical for patching and core key application. This note show how to collect and confirm the ODA serial Numbers for each server including the System Identifier also known as the Top Level Identifier (TLI) using oakcli commands, the ILOM and physical inspection.  A partial list of operations impacted by incorrect serial number registration is included for continued research.

Applies to:

Oracle Database Appliance X5-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X4-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 System Identifier, ODA Serial Number, OAKCLI, ODA X5-2, ODA X4-2, ODA X3-2, ODA V1, ILOM, IPMITOOL, oakcli show server

Goal

 How to identify the serial numbers found on the Oracle Database Appliance (ODA) 

Solution

There are two types of serial numbers used in the Oracle Database Appliance (ODA): The System Identifier and the individual component serial numbers

  • The most common serial number used for the ODA is called the System Identifier also known as the Top Level Identifier (TLI)
    - The System Identifier is required for Core Key generation and also checked during patching operations. 

  • The second serial number used is for each of the two individual servers* and storage array(s).
    - Individual component serial numbers are used during the initial registration of the ODA via My Oracle Support (MOS)

Note:    If you are using the ODA V1 please refer to the bottom section of this note for specific steps collection serial number information

ODA X3-2, X4-2 and X5-2 Servers

# oakcli show server

Issue the command as root on each of the two servers. 
If you are using Oracle Database Appliance Virtualized Platform (ODAVP) issue the command as root from Dom0
Note that the serial numbers on each server must match.

You can also check the serial numbers for the system and individual servers using the ILOM

# ipmitool -I open sunoem getval /X/system_identifier

If you cannot connect to the nodes for any reason you can still connect via the ILOM to confirm serial number information

For troubleshooting serial number mismatches or problems you inspect serial number entries for each asset and the System Identifier on MOS after ODA product registration has been completed.

 

Sample Outputs

login as: root

[root@oda~]# oakcli show server

Power State               : On
Open Problems             : 0
Model                     : ODA X3-2
Type                      : Rack Mount
Part Number               : 31683523+1+1
Serial Number             : 1234FM5678        <<
Primary OS                : Not Available
ILOM Address              : 10.141.132.97
ILOM MAC Address          : 00:10:E0:EF:CD:AB
Description               : ODA X3-2 V2 1234FM5678
Locator Light             : Off
Actual Power Consumption  : 258 watts
Ambient Temperature       : 26.750 degree C
Open Problems Report      : System is healthy 

 

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

Target Value: ODA X3-2 V2 1234FM5678

 


V1

Oracle first released the ODA V1 ( Sun Fire X4370 M2 Server ) as a single physical unit.
The V1 was delivered with all disks and the two servers enclosed in a single physical box unlike X3-2, X4-2, X5-2 which have independent servers (2) and storage enclosures (1 or optionally 2)

oakcli show server will not work for V1. Use the following command on each node instead

# /usr/sbin/dmidecode -t1 |grep Serial

# ipmitool sunoem getval /X/system_identifier

 

References

<NOTE:1638577.1> - ODA Troubleshooting ODA Core Key Generation and Application Problems
<NOTE: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
<NOTE:1280913.1> - How to update product serial number on systems which implement Top Level Identifier (TLI) functionality
<NOTE:1540755.1> - How to Replace an ODA (Oracle Database Appliance) System Controller Assembly
<NOTE:1447093.1> - Oracle Database Appliance - Steps to Generate a Key via MOS to change your CORE Count and apply this Core Key
<NOTE:1927384.1> - ODA Best Practices for ODA SR Creation : Mandatory Initial Data Collection with Examples

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback