Go to main content

Oracle® SuperCluster M8 and SuperCluster M7 Administration Guide

Exit Print View

Updated: June 2020

View the SP Configuration

When you reallocate resources using the osc-setcoremem command, osc-setcoremem saves the new configuration to the service processor (SP) in this format:



  • CM_ – indicates a core/memory configuration that was created sometime after the initial installation.

  • domx is expressed with this nomenclature:

    • xC or xS – CPU resources in number (x) of cores (C) or sockets (S)

    • xG or xT – Memory resources in number (x) of gigabytes (G) or number of terabytes (T)

  • TimeStamp – in the format MMDDYYYYHHMM

This file name example . . .


. . . represents a configuration created on August 20, 2015 at 13:54 and has three domains with these resources:

  • 2-sockets, 1-TB memory

  • 1-socket, 512 GB memory

  • 3-sockets, 1536 GB memory

To see more details about the resource allocations, you can use the SP configuration time stamp to locate and view the corresponding osc-setcoremem log file.

  1. Log in as superuser on the compute node's control domain.
  2. Display the SP configuration.


    • Output indicating no custom CPU/memory configurations:

      The file called V_B4_4_1_20150804141204 is the initial resource configuration file that was created when the system was installed.

      # ldm list-config
      V_B4_4_1_20150825155356 [next poweron]
    • Output indicating three additional CPU/memory configurations:

      # ldm list-config
      CM_1S1T_6C512G_082820151618 [current]
  3. View the corresponding log file.
    # more /opt/oracle.supercluster/osc-setcoremem/log/osc-setcoremem_activity_08-28-2015_16\:18*.log

Related Information