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
Type of Configuration PDomains
Allocating CPU Resources for LDoms
CPU Resources for LDoms Flowchart
Compute Server Level Considerations
Allocating Memory Resources for LDoms
Memory Resources for LDoms Flowchart
Compute Server Level Considerations
Understanding PCIe Cards and Slots for LDoms
PCIe Cards and Slots for LDoms Flowchart
Compute Server Level Considerations
Understanding Storage for LDoms
Compute Server Level Considerations
Understanding SuperCluster M6-32
Identifying SuperCluster M6-32 Components
Understanding the Compute Server
Understanding DCU Configurations
PCIe Device Root Complexes Overview
PCIe Communication and Paths Overview
Understanding DCU PCIe and EMS Slot Locations
Understanding Half-Populated DCU Root Complexes
Half-Populated DCU 0 PCIe Slot Root Complexes
Half-Populated DCU 1 PCIe Slot Root Complexes
Half-Populated DCU 2 PCIe Slot Root Complexes
Half-Populated DCU 3 PCIe Slot Root Complexes
Understanding Fully-Populated DCU Root Complexes
Fully-Populated DCU 0 PCIe Slot Root Complexes
Fully-Populated DCU 1 PCIe Slot Root Complexes
Fully-Populated DCU 2 PCIe Slot Root Complexes
Fully-Populated DCU 3 PCIe Slot Root Complexes
Extended Configuration PDomain Overview
Understanding Extended Configuration PDomains
Understanding Four DCUs in One Compute Server (R1 Extended Configuration PDomains)
Understanding Four DCUs Across Two Compute Servers (R2 Extended Configuration PDomains)
Understanding Base Configuration PDomains
Understanding Four DCUs on One Compute Server (R3 Base Configuration PDomains)
Understanding Four DCUs Across Two Compute Servers (R4 Base Configuration PDomains)
Understanding Two DCUs on One Compute Server (R5 Base Configuration PDomains)
Understanding Two DCUs Across Two Compute Servers (R6 Base Configuration PDomains)
Understanding Compute Server Hardware and Networks
CPU and Memory Resources Overview
LDoms and the PCIe Slots Overview
10GbE Client Access Network Overview
IB Network Data Paths for a Database Domain
IB Network Data Paths for an Application Domain
Understanding SR-IOV Domain Types
Understanding LDom Configurations for Extended Configuration PDomains
Understanding LDom Configurations for Fully-Populated DCUs (Extended Configuration PDomains)
Understanding LDom Configurations for Half-Populated DCUs (Extended Configuration PDomains)
Understanding LDom Configurations for Base Configuration PDomains
Understanding LDom Configurations for Fully-Populated DCUs (Base Configuration PDomains)
Understanding LDom Configurations for Half-Populated DCUs (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
SPARC: Server-Specific and New Oracle ILOM Features and Requirements
Unsupported Oracle ILOM Features
Oracle ILOM Remote Console Plus Overview
Oracle Hardware Management Pack Overview
Time Synchronization and NTP Service
The IB network connects the compute servers, storage appliance, and storage servers using the IB HCAs installed in the PCIe slots in each DCU and the IB switches installed in the expansion rack. This nonroutable network is fully contained in SuperCluster M6-32, and does not connect to your existing network.
When SuperCluster M6-32 is configured with the appropriate types of LDoms, the IB network is partitioned to define the data paths between the compute servers, and between the compute servers and the storage appliances.
The defined IB data path coming out of the compute servers varies, depending on the type of LDom created: