####################################################################
# How to reduce the number of active CPU cores on ODA system
####################################################################
--Find the ODA Serial Number [root@odanode1 ~]# /usr/sbin/dmidecode -t1 |grep Serial Serial Number: 1xxxxxXXXXxG
--Login to MOS and generate the CPU Key using the ODA Serial Number.
#################################################################### ## ODA CPU Capping ####################################################################
------------------------------------
-- Target active CPU cores --
------------------------------------
HOSTNAME | CPU COUNT
---------------|----------------
odanode1 | 6
---------------|----------------
odanode2 | 6
--------------------------------
------------------------------------------------------------------------------- --Reduce the CPU cores running the following command from the first node only! ------------------------------------------------------------------------------- /opt/oracle/oak/bin/oakcli show core_config_key /opt/oracle/oak/bin/oakcli apply core_config_key /tmp/CPU_KEY
------------------------------------------ --Activity Log ------------------------------------------ [root@odanode1 tmp]# vi CPU_KEY <--- Store the CPU key generated on MOS [root@odanode1 tmp]# /opt/oracle/oak/bin/oakcli show core_config_key Optional core_config_key is not applied on this machine yet ! [root@odanode1 tmp]# pwd /tmp [root@odanode1 tmp]# /opt/oracle/oak/bin/oakcli apply core_config_key /tmp/CPU_KEY INFO: Both nodes get rebooted automatically after applying the license Do you want to continue: [Y/N]?: Y INFO: User has confirmed the reboot
Please enter the root password:
............done
INFO: Applying core_config_key on '192.168.16.25' ... INFO : Running as root: /usr/bin/ssh -l root 192.168.16.25 /tmp/tmp_lic_exec.pl INFO : Running as root: /usr/bin/ssh -l root 192.168.16.25 /opt/oracle/oak/bin/oakcli enforce core_config_key /tmp/.lic_file Waiting for the Node '192.168.16.25' to reboot........................... Node '192.168.16.25' is rebooted Waiting for the Node '192.168.16.25' to be up before applying the license on the node '192.168.16.24'. ............................................. INFO: Applying core_config_key on '192.168.16.24' ... INFO : Running as root: /usr/bin/ssh -l root 192.168.16.24 /tmp/tmp_lic_exec.pl INFO : Running as root: /usr/bin/ssh -l root 192.168.16.24 /opt/oracle/oak/bin/oakcli enforce core_config_key /tmp/.lic_file
Broadcast message from root (Fri Jun 7 15:18:34 2013):
The system is going down for reboot NOW! [root@odanode1 tmp]#
------------------------------------------------------------- --Check the new Number of active cores -------------------------------------------------------------
[root@odanode1 ~]# /opt/oracle/oak/bin/oakcli show core_config_key
Host's serialnumber = 1xxxxxXXXXxG Enabled Cores (per server) = 6 Total Enabled Cores (on two servers) = 12 Server type = V1 -> SUN FIRE X4370 M2 Hyperthreading is enabled. Each core has 2 threads. Operating system displays 12 processors per server [root@odanode1 ~]#
Hi,
I want to ask about ODA V1. After run oakcli apply core_config_key, when run top command it show all 24 cpu core. But in ODA X3-2, when run top command it only show cpu core count according to apply core_config_key. Is it normal on oda v1 to show all cpu usage when run top command?
LikeLike
Hi,
I don’t think this is correct behaviour. I’m not working with the ODA since few years, but I remember that the CPU Cores cupping happens at BIOS level, hance the OS will be able to see only what is enable.
LikeLike