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)
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
The tool tracks resource allocation and ensures that the selections you make are valid. This section describes how the minimum and maximum resources are determined.
This table summarizes the minimum resource requirements for dedicated domains on SuperCluster M6-32:
|
The minimum amount of CPU resource that can be assigned to a dedicated domain is determined by the number of IB and 10GbE devices in the domain (2 cores are required per IB HCA)
The minimum amount of memory that can be assigned to a dedicated domain is determined as follows:
The number of IB and 10GbE devices in the domain (2 16GB memory granules are required per IB HCA)
The number of cores assigned to the domain (one 16GB granule in the same locality group is required per 4 additional cores)
The maximum amount of CPU resource that can be assigned to a dedicated domain is determined by the amount of resources available after taking these points into account:
Resources already assigned to other dedicated domains
Required minimal resource for dedicated domains with no resource yet assigned
The maximum amount of memory resources that can be assigned to a dedicated domain is determined by the amount of resources available after taking these points into account:
Resources already assigned to other dedicated domains
Required minimum resources for dedicated domains with no resource yet assigned
The requirement that for each dedicated domain a memory granule footprint is placed in all locality groups with allocated cores