How to configure Oracle Private Cloud Appliance with additional Memory.

Asset ID:	1-71-2011566.1
Update Date:	2017-05-30
Keywords:

Solution Type Technical Instruction Sure

Solution 2011566.1 : How to configure Oracle Private Cloud Appliance with additional Memory.

Applies to:

Private Cloud Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Private Cloud Appliance - Version 2.0.5 to 2.0.5 [Release 2.0]
Information in this document applies to any platform.
Private Cloud Appliance minimum required version 2.0.4.

Goal

This note describes what changes are needed after increasing the base RAM in an Oracle Private Cloud Appliance Compute Node. There are no changes made within Oracle VM Manager, the change is on each Compute Node that has had its RAM increased.

The RAM part number is P/N 7110356 - One 32 GB LR DDR4-2133 DIMM

The installation of the RAM upgrade will need to be completed by Field or ACS services. SKU B63937

Solution

If total RAM is increased to 512 GB set dom0_mem=11264M

If total RAM is increased to 768 GB set dom0_mem=16512M

The following change is not persistent during a Compute Node re-provision, and must be reapplied once re-provisioning has completed.

Once the RAM has been installed into the Compute Node edit /etc/grub.conf in each Compute Node with additional RAM.

In the following sample of a default Compute Node grub.conf replace the dom0_mem= value of 5888M with the correct value for the amount of RAM installed from above.

[root@ovcacn07r1 ~]# cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
title Oracle VM Server (2.6.39-400.249.3.el5uek)
root (hd0,0)
kernel /xen.gz console=com1,vga com1=9600,8n1 dom0_mem=5888M dom0_vcpus_pin dom0_max_vcpus=16 allowsuperpage crashkernel=256M@64M
module /vmlinuz-2.6.39-400.249.3.el5uek ro root=UUID=26e23853-f5d7-4149-96dd-9e11ace40ce0 console=hvc0 console=tty0 console=xvc0 swiotlb=131072
module /initrd-2.6.39-400.249.3.el5uek.img
title Oracle VM Server-ovs (xen-4.1.3 2.6.39-300.32.5.el5uek)
root (hd0,0)
kernel /xen.gz dom0_mem=5888M dom0_vcpus_pin dom0_max_vcpus=16 allowsuperpage crashkernel=256M@64M
module /vmlinuz-2.6.39-300.32.5.el5uek ro root=UUID=26e23853-f5d7-4149-96dd-9e11ace40ce0 console=tty0 console=xvc0 swiotlb=131072
module /initrd-2.6.39-300.32.5.el5uek.img
title Oracle VM Server-ovs serial console (xen-4.1.3 2.6.39-300.32.5.el5uek)
root (hd0,0)
kernel /xen.gz console=com1,vga com1=9600,8n1 dom0_mem=5888M dom0_vcpus_pin dom0_max_vcpus=16 allowsuperpage crashkernel=256M@64M
module /vmlinuz-2.6.39-300.32.5.el5uek ro root=UUID=26e23853-f5d7-4149-96dd-9e11ace40ce0 console=hvc0 console=tty0 console=xvc0 swiotlb=131072
module /initrd-2.6.39-300.32.5.el5uek.img

Once the above changes have been implemented, a reboot of the Compute Node is required for the changes to take affect.

Additionally a Management Node change is required for provisioning and re-provisioning of Compute Nodes. This change is currently not persistent after a Private Cloud Appliance upgrade.

Provisioning or re-provisioning of the Compute Nodes with additional RAM will fail as described in http://docs.oracle.com/cd/E19045-01/blade.x6450/820-3538-23/software.html (RHEL 5.0 Panics During Boot With More Than 64 GB Memory)

To resolve the above provisioning/re-provisioning issue logon to the active Management Node and modify "/nfs/shared_storage/pxe_templates/pxelinux_cfg_OVM_template" as shown below by adding "dom0_mem=5888M" this change works with all installed RAM options.

[root@ovcamn05r1 ~]# cat /nfs/shared_storage/pxe_templates/pxelinux_cfg_OVM_template
default OVCA-COMPUTE-OVM-1
LABEL OVCA-COMPUTE-OVM-1
KERNEL OVM/mboot.c32
APPEND OVM/xen.gz dom0_mem=5888M --- OVM/vmlinuz ks=nfs:XXXNFS_IPXXX:/export/MGMT_ROOT/kickstart/XXXKICKSTART_FILEXXX ksdevice=eth0 linksleep=50 --- OVM/initrd.img
[root@ovcamn05r1 ~]#

Attachments

This solution has no attachment