Oracle Database Appliance X4-2
 
Oracle Database Appliance
 
Oracle Database Appliance X3-2
 
Oracle Database Appliance X5-2
 
Oracle Database Appliance Software
 

PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
 
_Old GCS Categories>ST>Server>Engineered Systems>Oracle Database Appliance>Install
 

Steps to apply Core Key on the Oracle Database Appliance

In this Document

Goal

OVERVIEW

Solution

Rules and Restrictions for Changing the CPU Core Count (Bare Metal)

Steps: Example of Creating or Changing the ODA CPU Core Count including generating a Core Key

References

Applies to:

Goal

Steps by Step instructions to Configure the Oracle Database Appliance CPU Core Count for Oracle Database Appliance V1, X3-2, X4-2 and X5-2

For X6-2 and higher please refer to Note 2220572.1:
ODA: X6-2 Capacity-On-Demand : How To Change & Register CPU Cores For Single-Node ODA Lite X6-2(S,M,L) or the Dual-Node ODA HA

OVERVIEW 

This document discusses how to configure the Oracle Database Appliance CPU core count. The CPU core count is the number of enabled CPU cores per server

This note provides step by step instructions from the graphic interface via My Oracle Support to change the CPU Core Count for your Oracle Database Appliance ( ODA )

Requirements:

• CSI created for the ODA and registered on MOS (My Oracle Support)
  
  

The Single ODA System Identifier / Serial Number for X3-2, X4-2 and X5-2 (There is one matching serial# on both physical ODA blades)
- ODA V1 uses different serial numbers found on each Node within the same physical box

For X5-2 X4-2 and X3-2 using 12.1.2.x.x and higher you can use the command oakcli show server on BOTH nodes as the serial numbers must match each other.

Sometimes the customer will follow all steps in this note and still be unable to GENERATE a Core Key.

INTERNAL for SUPPORT Add:

• SR#
• Account Name and
• CSI#

Support: When requesting a new core key for a customer who is unable to GENERATE a Core Key please get the external and above information from the customer
Send the above information in an email requesting a new Core Key to chuck.lucas@oracle.com cc:   jiong.dai@oracle.com ;  David LaPoint@oracle.com

•  Optionally: If the Oakcli command is not working

  
  For X5-2 X4-2 and X3-2 please issue the following on both Nodes of the ODA as root to confirm these are as expected
       
  oakcli show server
  
        Optionally
  
  ipmitool -I open sunoem getval /X/system_identifier
  
      Target Value: Oracle Database Appliance X4-2 1456ABC12A
  
  
  
  For ODA V1 (SUN FIRE X4370 M2 SERVER) issue the following on both Nodes -- the V1 requires both unique serial numbers unlike the Single SYSTEM level Serial number for the newer ODA Versions
  
  
  [root@oda1 ~]# dmidecode -t1 | grep Serial
  
          Serial Number: 123ABC123               << Should be the same for each node
  
  
  
  
• Steps via MOS to find your Asset (using the serial # for the ODA box ) -- see the example
  
  To determine your ODA HW version you can issue the following (as root)
  
  fwupdate list sp_bios
   
  
  ODA X5-2, X4-2 or X3-2
  
  root@oda1    -- X4-3 Example
  
  ==================================================
  SP + BIOS
  ==================================================
  ID               Product Name                  ILOM Version                  BIOS/OBP Version              XML Support
  ---------------------------------------------------------------------------------------------------------------
  sp_bios        SUN SERVER X4-2               v3.1.2.30.a r83840            25010601                            N/A 
    
  
  V1 (X4370 M2)
  root@odav1
  
  [root@oda1 ~]# 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.d r83408           12010311                      N/A    
   
  
  
• Choose your Core count to be set for the first time OR to increase your core count from an existing value
  
  You should see the Core Key Generation option if you are the ODA MOS CSI admin
  
  Serial Number
  Hardware Type
  Cores per Server     In sets of 2  
  -- Generate Key
  Cores per Appliance  -- will be automatically calculated at 2x the above value
   

Solution

Rules and Restrictions for Changing the CPU Core Count (Bare Metal)

• After you SET a CPU core count for the ODA, then you can only increase subsequent CPU core counts
• You can change the CPU core count to 2,4,6,8,10 or 12 per server on V1 for a total of 24 cores (default)
• You can change the CPU core count to 2,4,6,8,10,12 or 16** per server on X3-2 for a total of 32 cores (default)**
• You can change the CPU core count to 2,4,6,8,10,12,14,16,18,20,22 or 24 per server on X4-2 for a total of 48 cores (default)*
• You can change the CPU core count to increments of 2 from 2 up to 36 per server on X5-2 for a total of 72 Cores
• Core Counts should be the same (matched count) on each server
  
  
  
    * If you are changing from Bare Metal to Virtualization on ODA you must remove the Core Key (see the associated patchset README for more details )
  **  If you are using an older ODA version X3-2 + 2.8 or older cpu counts are al 4 per server are required on the BARE METAL X3-2 due to a processor chip limitation. This was fixed in 2.9 and higher the X3-2 can update at increments of 2 CPUs per node.
          2.8 or lower: sets of 4 per server
          2.10 or higher: Does allow increments of two per server
  http://docs.oracle.com/cd/E22693_01/doc.12/e25375/chapter2.htm#CMTLI2261
  
  Each ODA consists of two servers ( for the ODA-HA series)
       X5-2,X4-2  and X3-2 number of Cores and can be incremented in sets of 2 per server up to the maximum of 72,48 and 32 respectively per ODA (both servers) **
  

For Example:

Steps: Example of Creating or Changing the ODA CPU Core Count including generating a Core Key

If you change the core count after the initial deployment, be aware that changing the core count causes both servers to restart. After the initial deployment, plan and carry out the core count change at a suitable time where the availability impact is minimized.

To change the CPU core count:

1. Log in to the My Oracle Support at: https://myoraclesupport.com
   
   
2. Click the Settings tab and select Assets from the submenu.
   
   
3. Search for the serial number of the appliance in the asset list.  (If you cannot locate the serial number, then contact Oracle Support.)
   
   
   
4. Select the serial number of the appliance and click on "Core Configuration"in the Asset Details Screen
   
   
5. Select Manage Key... from the available actions.
   
   
6. In the Manage Cores Configuration Key dialog box, you can view the serial number of the appliance. If a key was previously generated, then you can view the current configuration. 
   1. In the Cores Per Server list, select the desired number of enabled CPU cores per server. The value you select will apply to both servers on the appliance. Initially, you can select 2, 4, 6, 8, 10, or 12.
      
      

      Subsequently, you can only select a number that is greater than the current number.

   2. Click Generate Key to generate the key.
      
      
   3. Click Copy Key to Clipboard to copy the key to the clipboard.
      
      
7. Paste the key into an empty text file and save the file to a location on the Oracle Database Appliance.
8. Log in to the first node of the servers on the Oracle Database Appliance as root.
   

   Note:
   • Customer should not attempt editing the generated key using any tools
   • Customer could move the key to the Appliance using scp in binary mode.
   • Open a Terminal session or xterm and Login as root
   • Execute the oakcli apply core_config_key command as root

9. The command in this step will reboot the server to complete the reconfiguration.
   
   Run the following command:
   
   
   # /opt/oracle/oak/bin/oakcli apply core_config_key /key_file_location/core_key_filename
    
   Where key_file_location is the full path name of the text file that you created in Step 6.
   
   For example:
   
   
   # /opt/oracle/oak/bin/oakcli apply core_config_key /tmp/dis/core_key4

   
   

10. After the system restarts, Oracle Database Appliance will be reconfigured and both servers will be running with the specified CPU core count.
    
    # /opt/oracle/oak/bin/oakcli show core_config_key
    Host's serialnumber = 01234AB56C7
    Configured Cores = 20
    
    Note: The CPU’s in the Database Appliance are hyper threaded, so when verifying the number of CPU cores with the cpuinfo command, you will see two times (2X) the number of cores configured pre server. For example, In this note we configured 10 cores per server, for a total of 20 cores for the appliance, so the cpuinfo command will return the following:

# cat /proc/cpuinfo | grep -i processor
processor : 0
processor : 1
processor : 2
processor : 3
processor : 4
processor : 5
processor : 6
processor : 7
processor : 8
processor : 9
processor : 10
processor : 11
processor : 12
processor : 13
processor : 14
processor : 15
processor : 16
processor : 17
processor : 18
processor : 19
...
...    -- The maximum number of cores available is HW version dependent
...

 

FOR SUPPORT and SALES
----------------------------------
1. Customer Admin needs to add the Hardware CSI into the MOS Profile and choose the correct Company name [ For Global Organization] and then Click - Request Access-

2. Under Accounts and Privileges: The CSI Status turns to - Pending Oracle Approval -

         [ The support SLA is from 2 hours to 24 hours]

    a. Support checks that the CSI admin user email id has the same domain as the Company.
       That means the Partners would not be able to generate the core key for their
       customers using their email id.
    b. It may be a good idea to call the Support Hotline and follow up on the status and advice

3. An email is sent to the Admin giving the details of the CSI Request and if it is Approved ?

4. If not logging out of the MOS , then remember to REFRESH the page 

5. Once the CSI shows the status as -Approved- you are ready to generate the Core key

 There has been a transition from MOS using FLASH vs. HTML. During the transition several  users experienced problems altering the CORE COUNT using HTML. This problem has been fixed so it is no longer a problem creating the CORE COUNT KEY using HTML. Please report any new Core Key Count generation problems using HTML to the ODA email list

Community Discussions

Still have questions? Use the communities window below to search for similar discussions or start a new discussion on this subject. (Window is the live community not a screenshot)

Click here to open in main browser window

References

This solution has no attachment