![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 2095097.1 : ODA How To Identify the Serial Number for the Oracle Database Appliance
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 GoalHow to identify the serial numbers found on the Oracle Database Appliance (ODA) SolutionThere are two types of serial numbers used in the Oracle Database Appliance (ODA): The System Identifier and the individual component serial numbers
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 serverIssue the command as root on each of the two servers. You can also check the serial numbers for the system and individual servers using the ILOM # ipmitool -I open sunoem getval /X/system_identifierIf 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
[root@oda~]# ipmitool -I open sunoem getval /X/system_identifier
Target Value: ODA X3-2 V2 1234FM5678
V1Oracle first released the ODA V1 ( Sun Fire X4370 M2 Server ) as a single physical unit. 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_identifierReferences<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 |
||||||||||||
|