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)
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
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
ASR automatically opens service requests when specific hardware faults occur. In many cases, Oracle Support Services can begin resolving the issue immediately, often before the system administrator is aware that a problem exists.
The telemetry data that is sent from the ASR Manager to Oracle is encrypted.
When ASR detects a fault, ASR sends an email message to your MOS email account for ASR, and to the technical contact for the activated asset, notifying them of the creation of the service request.
To enable this feature, ASR Manager software must be installed on a server (a server other than SuperCluster). The ASR Manager server must have connectivity to SuperCluster, and an outbound Internet connection using HTTPS or an HTTPS proxy. Certain SuperCluster components must be configured to send hardware fault telemetry to the ASR Manager server.
For SuperCluster systems, ASR uses these telemetry sources to detect fault events:
FMA – Provides CPU and memory fault information from the host.
Oracle ILOM – Provides fault information, power and environmental, and CPU and memory fault information from the service processor.
Exadata-detected Events (HALRT) – Provides fault coverage for disks, flash, and PCI cards within Oracle SuperCluster.
ZFS storage appliance – Provides fault events detected within the systems and disk arrays of the included Storage Appliance.
IB switch management module – Provides fault coverage for power, memory, storage, and battery.
Consider this information when using ASR:
ASR is applicable only for component faults. Not all component failures are covered, however components that are most likely to generate faults, such as disks, fans, and power supplies, are covered by ASR.
ASR is not a replacement for other monitoring mechanisms, such as SMTP and SNMP alerts. ASR is a complementary mechanism that expedites and simplifies the delivery of replacement hardware. ASR should not be used for downtime events in high-priority systems. For high-priority events, contact Oracle Support Services directly.
There are occasions when a service request might not be automatically filed. This can happen due to problems with the SNMP protocol or loss of connectivity to the ASR Manager. You must continue to monitor the systems for faults and call Oracle Support Services if you do not receive notice that a service request has been automatically filed.