Understanding SuperCluster Software
Identify the Version of SuperCluster Software
Controlling SuperCluster M6-32
Powering Off SuperCluster M6-32 Gracefully
Shut Down the Oracle Solaris Cluster
Shut Down the Enterprise Controller (Ops Center)
Shut Down the OS on the Compute Servers
Shut Down the ZFS Storage Appliance
Power Off the Switches and Racks
Power Off SuperCluster M6-32 in an Emergency
Monitoring SuperCluster M6-32 (OCM)
Monitoring the System With ASR
Configure ASR on the Compute Servers (Oracle ILOM)
Configure SNMP Trap Destinations for Storage Servers
Configure ASR on the ZFS Storage Appliance
Configuring ASR on the Compute Servers (Oracle Solaris 11)
Enable the HTTP Receiver on the ASR Manager
Enable HTTPS on ASR Manager (Optional)
Register Compute Servers With Oracle Solaris 11 or Database Domains to ASR Manager
Approve and Verify ASR Asset Activation
Change ssctuner Properties and Disable Features
Configuring CPU and Memory Resources (osc-setcoremem)
Minimum and Maximum Resources (Dedicated Domains)
Supported Domain Configurations
Plan CPU and Memory Allocations
Display the Current Domain Configuration (osc-setcoremem)
Display the Current Domain Configuration (ldm)
Change CPU/Memory Allocations (Socket Granularity)
Change CPU/Memory Allocations (Core Granularity)
Access osc-setcoremem Log Files
Revert to a Previous CPU/Memory Configuration
Remove a CPU/Memory Configuration
Obtaining the EM Exadata Plug-in
Known Issues With the EM Exadata Plug-in
Configuring the Exalogic Software
Prepare to Configure the Exalogic Software
Enable Domain-Level Enhancements
Enable Cluster-Level Session Replication Enhancements
Configuring Grid Link Data Source for Dept1_Cluster1
Runtime Connection Load Balancing
Secure Communication With Oracle Wallet
Create a Grid Link Data Source on Dept1_Cluster1
Configuring SDP-Enabled JDBC Drivers for Dept1_Cluster1
Configure the Database to Support IB
Create an SDP Listener on the IB Network
Administering Oracle Solaris 11 Boot Environments
Advantages to Maintaining Multiple Boot Environments
Mount to a Different Build Environment
Reboot to the Original Boot Environment
Create a Snapshot of a Boot Environment
Remove Unwanted Boot Environments
Monitor Write-through Caching Mode
SuperCluster compute server CPU and memory resources are initially allocated during installation as defined by your configuration. CPU sockets are assigned to domains in the same proportion as IB HCAs. Memory is assigned in the same proportions.
The osc-setcoremem tool enables you to migrate CPU cores and memory resources between dedicated domains, and from dedicated domains to CPU and memory repositories for the use of IO domains.
These points provide important information related to the use of osc-setcoremem:
The final CPU and memory layout for a dedicated domain is optimized for locality to minimize accesses to non-local resources.
The granularity of CPU and memory migration is 1 core and 16GB.
Empty dedicated domains (domains with zero cores and zero memory) are not supported.
The tool tracks resource allocation and ensures that the selections you make are valid. See Minimum and Maximum Resources (Dedicated Domains).
Affected dedicated domains must be rebooted after any change.
The tool enables you to change the CPU and memory allocations in one of two levels of granularity:
Socket granularity – The tool automatically allocates each domain a minimum of one socket, then enables you to allocate remaining sockets to the domains. See Change CPU/Memory Allocations (Socket Granularity).
Core granularity – The tool automatically allocates each domain a minimum number of cores, then enables you to allocate additional cores in one-core increments. See Change CPU/Memory Allocations (Core Granularity).
If you configure the CPU and memory resources so that some resources are not allocated to any domain, those unallocated resources are parked. Parked resources are placed in a logical CPU and memory repository and are available for I/O Domains. See Park Cores and Memory.
You can park resources from dedicated domains anytime, but you cannot move parked resources to dedicated domains once I/O Domains are created.
Also see Supported Domain Configurations.