ODAVP X5-2 or X4-2 : Invalid -maxvcpu Values when Trying to Set vCPUs to Over 32 Using " oakcli configure vm ..."

Asset ID:	1-72-1999258.1
Update Date:	2016-04-12
Keywords:

Solution Type Problem Resolution Sure

Solution 1999258.1 : ODAVP X5-2 or X4-2 : Invalid -maxvcpu Values when Trying to Set vCPUs to Over 32 Using " oakcli configure vm ..."

Related Items


Oracle Database Appliance X4-2
 Oracle Database Appliance X5-2

Related Categories


PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST

oakcli configure vm dcapp_server -vcpu 32  -maxvcpu 40
ERROR: invalid -maxvcpu values
Usage:
oakcli configure vm  [-vcpu  -maxvcpu  -cpuprio  -cpucap  -memory  -maxmemory  -os  -keyboard  -mouse  -domain  -network  -autostart  -disk  -bootoption  -cpupool  -prefnode  -failover ]
where:
         vm                    - configures a vm
         -vcpu                 - (1-32) num. of cpu's assigned to the VM|VMTemplate
         -maxvcpu              - (1-32) maximum #cpu's the VM|VMTemplate can consume
         -cpuprio              - (1-65535) large value has high priority

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]
Information in this document applies to any platform.

Symptoms

As per documentation, it says
Number of nodes assigned to the virtual machine. This number depends on your Oracle Database Appliance configuration:

• On Oracle Database Appliance X5-2, the range is from 1 to 72
• On Oracle Database Appliance X4-2, the range is from 1 to 48

However, choosing a value over 32 vCPU for the ODA you encounter errors

Example: Attempt to configure 40 maxvcpu or any number of v*cpu beyond 32 results in errors

oakcli configure vm dcapp_server -vcpu 32 -maxvcpu 40

ERROR: invalid -maxvcpu values

Usage:
oakcli configure vm <name> [-vcpu <x> -maxvcpu <x> -cpuprio <x> -cpucap <x> -memory <x> -maxmemory <x> -os <x> -keyboard <x> -mouse <x> -domain <x> -network <x> -autostart <x> -disk <x> -bootoption <x> -cpupool <poolname> -prefnode <x> -failover <x>]
where:
         vm                    - configures a vm
         -vcpu                 - (1-32) num. of cpu's assigned to the VM|VMTemplate
         -maxvcpu           - (1-32) maximum #cpu's the VM|VMTemplate can consume
         -cpuprio              - (1-65535) large value has high priority

Changes

NONE

Cause

Current -vcpu and -maxvcpu values are capped to a hard value of 32 even though the stated range is 48 or 72 for the X4-2 and X5-2 respectively.

This problem is an Internal Bug:20961360 which prevents the proper processing of -vcpu or maxvcpu values over 32 using oakcli on the X4-2 and X5-2 ODA configurations.

The fix for this bug is included in 12.1.2.7.

Solution

As a workaround you can manually update the v*cpu counts in oda_base:

This example shows how to set 38 which exceeds the current hard limit using oakcli of 32.

# cd /opt/oracle/oak/adapters/
# export CmdUniqId='configurevm'
# export _OAK_Name=<vm name>
# export _OAK_NodeNum=0
# export Vcpu=38 ==============> If you need 38. If you are using below 32, you don't need to change anything. Set this value as per your need.
# export MaxVcpu=38 ==============>
# ./OvmAdapter.scr configure

This will update the vm.cfg and metadata correctly.
The changes will be effective after restart of the vm.
The "oakcli show vm <vm>" will continue to show old value till the next restart of the oakd.

References

<BUG:20961360> - MISSING OPTION TO ACTIVATE 20 CORES FOR ODA BASE ON ODA X5-2 VIRTUAL PLATFORM
<BUG:20954520> - LNX64-112-CMT: CONFIGURE ODA_BASE CORE LICENSE OPTION

Attachments

This solution has no attachment