| Skip Navigation Links | |
| Exit Print View | |
|
Oracle SuperCluster M6-32 Owner's Guide: Administration |
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
The ssctuner utility is a small set of Perl and Korn shell scripts and configuration files that run on SuperCluster Oracle Solaris 10 and Oracle Solaris 11 global zones. By default, ssctuner is installed and enabled at installation time.
The utility runs in realtime as an SMF service to monitor and tune ndd parameters and various system configuration parameters including these files:
/etc/system
/kernel/drv/sd.conf
/kernel/drv/ssd.conf
/etc/inet/ntp.conf
The utility also periodically checks for the use of DISM or suboptimal NFS mount options.
By default, the utility runs every two hours and modifies parameters as needed.
The utility also checks every two minutes to see if there are any virtual disk devices that were in a degraded state and have come back online, and if so, clears that zpool.
Note - If you manually tune a parameter for which ssctuner requires a different value, ssctuner sets the value of that parameter back to what ssctuner requires and logs the changes at this interval check. If you must control one or more of the parameters ssctuner manages, consider turning off those specific components rather than disabling ssctuner completely. See Change ssctuner Properties and Disable Features.
Note - Oracle Solaris 11 must be at SRU 11.4 or later, or ssd.conf/sd.conf settings might cause panics.
Note - Do not set ndd parameters through another SMF service or init script. ssctuner must manage the ndd parameters.
|