Determining SuperCluster M6-32 Configurations
Determine the Number of Compute Servers
Determine the Number of DCUs in Each Compute Server
Determine the Number of CMUs in Each DCU
Determine the Amount of Memory in Each DCU
Determine the PDomain Configuration on Each Compute Server
Determine the LDom Configuration for Each PDomain
Determining the Best Configuration for Your Situation
Understanding PDomain Configurations
Allocating CPU Resources for LDoms
Allocating Memory Resources for LDoms
Understanding PCIe Cards and Slots for LDoms
Understanding Storage for LDoms
Understanding SuperCluster M6-32
Identifying SuperCluster M6-32 Components
Understanding DCU Configurations
Understanding Half-Populated DCU Root Complexes
Understanding Fully-Populated DCU Root Complexes
Extended Configuration PDomain Overview
Understanding Extended Configuration PDomains
Understanding Base Configuration PDomains
Understanding Compute Server Hardware and Networks
Understanding LDom Configurations for Extended Configuration PDomains
Understanding LDom Configurations for Base Configuration PDomains
Understanding Clustering Software
Cluster Software for the Database Domain
Cluster Software for the Oracle Solaris Application Domains
Understanding System Administration Resources
Understanding Platform-Specific Oracle ILOM Features
Oracle ILOM Remote Console Plus Overview
Oracle Hardware Management Pack Overview
Time Synchronization and NTP Service
Multidomain Extensions to Oracle ILOM MIBs
Hardware Installation Overview
Hardware Installation Task Overview
Hardware Installation Documents
Preparing the Site (Storage Rack and Expansion Racks)
Prepare the Site for the Racks
Network Infrastructure Requirements
Compute Server Default Host Names and IP Addresses
Compute Server Network Components
Storage Rack Network Components
Cable the ZFS Storage Appliance
ZFS Appliance Power Cord Connection Reference
ZFS Storage Appliance Cabling Reference
Leaf Switch 1 Cabling Reference
Leaf Switch 2 Cabling Reference
IB Switch-to-Switch Cabling Reference
Cable the Ethernet Management Switch
Ethernet Management Switch Cabling Reference
Connect SuperCluster M6-32 to the Facility Networks
Expansion Rack Default IP Addresses
Understanding Internal Cabling (Expansion Rack)
Understanding SuperCluster Software
Identify the Version of SuperCluster Software
Controlling SuperCluster M6-32
Powering Off SuperCluster M6-32 Gracefully
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)
Approve and Verify ASR Asset Activation
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
Configuring SDP-Enabled JDBC Drivers for Dept1_Cluster1
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
![]() | Caution - Do not perform this procedure without Oracle Support approval. Changing properties or disabling ssctuner features can have unpredictable consequences. |
Changing certain ssctuner properties such as EMAIL_ADDRESS and disk or memory usage warning levels might be advantageous in some environments.
# svccfg -s ssctuner listprop 'ssctuner_vars/*' ssctuner_vars/CRIT_THREADS_FIX boolean true ssctuner_vars/CRIT_THREADS_NONEXA boolean false ssctuner_vars/DISK_SPACE_CHECK boolean true ssctuner_vars/DISK_USAGE_CRIT integer 90 ssctuner_vars/DISK_USAGE_WARN integer 85 ssctuner_vars/DISM_CHECK boolean true ssctuner_vars/EMAIL_ADDRESS astring root@localhost ssctuner_vars/EMAIL_MESSAGES boolean true ssctuner_vars/FORCELOAD_VDC boolean false ssctuner_vars/INTRD_DISABLE boolean true ssctuner_vars/ISCSI_TUNE boolean true ssctuner_vars/MAJOR_INTERVAL integer 120 ssctuner_vars/MEM_USAGE_CRIT integer 97 ssctuner_vars/MEM_USAGE_WARN integer 94 ssctuner_vars/MINOR_INTERVAL integer 2 ssctuner_vars/NDD_TUNE boolean true ssctuner_vars/NFS_CHECK boolean true ssctuner_vars/NFS_EXCLUDE astring ssctuner_vars/NFS_INCLUDE astring ssctuner_vars/NTPCONF_TUNE boolean true ssctuner_vars/POWERADM_DISABLE boolean true ssctuner_vars/SDCONF_TUNE boolean true ssctuner_vars/SERD_THRESHOLD_TUNE boolean true ssctuner_vars/SSDCONF_TUNE boolean true ssctuner_vars/SYSLOG_DUP_SUPPRESS_HOURS integer 8 ssctuner_vars/SYSTEM_TUNE boolean true ssctuner_vars/ZPOOL_FIX boolean true ssctuner_vars/ZPOOL_NAME_CUST astring
These are examples of properties you might need to change:
Configure the system so that critical messages are sent to your email address.
~# svccfg -s ssctuner setprop ssctuner_vars/EMAIL_ADDRESS="my_name@mycorp.com"
Change the disk (/ and zone roots) usage warning level to 80%.
~# svccfg -s ssctuner setprop ssctuner_vars/DISK_USAGE_WARN=80
Enable thread priority changing for non-exa Oracle DB domains:.
~# svccfg -s ssctuner setprop ssctuner_vars/CRIT_THREADS_NONEXA=true
Enable zpool check and repair of vdisk zpools that are not generated by the SuperCluster installer.
~# svccfg -s ssctuner setprop ssctuner_vars/ZPOOL_NAME_CUST=my_vdisk_pool
Exclude NFS mounts from warning mechanisms.
~# svccfg -s ssctuner setprop ssctuner_vars/NFS_EXCLUDE='mount_name_or_device'
Include NFS mounts in warning mechanism (overrides exclude).
~# svccfg -s ssctuner setprop ssctuner_vars/NFS_INCLUDE='mount_name_or_device'
Disable all NFS mount warnings (not recommended).
~# svccfg -s ssctuner setprop ssctuner_vars/NFS_CHECK=false
The NFS_EXCLUDE, NFS_INCLUDE and ZPOOL_NAME_CUST properties must be simple strings but you can use simple regular expressions.
If you need the flexibility of regular expressions, be extremely careful to double quote the expressions. Also verify that the ssctuner service comes back after restarting and no errors are in the SMF log file.
# svcadm restart ssctuner
If you changed a property using an incorrect syntax, the service does not come back. If this happens, identify the offending property that you must fix:
# grep -i parameter /var/svc/log/site-application-sysadmin-ssctuner:default.log
After making any corrections or changes, repeat Step 3.