Understanding the System Architecture
Understanding PCIe Device Root Complexes
Control Domain and Reserved Root Complexes
Fully-Populated Default Configuration
Understanding PCIe Slot Root Complex Names and Device Paths
PCIe Device Root Complex Failover Behavior
Understanding EMS SAS Paths to the Internal Drives
SAS Paths From EMS Module to Drives
Understanding Internal Drive Device Paths
HDD and SSD Device Path Differences
Understanding DCU0 Drive Device Paths
Understanding DCU1 Drive Device Paths
Understanding DCU2 Drive Device Paths
Understanding DCU3 Drive Device Paths
Understanding Network Port Device Paths
DCU0 Network Port Device Paths
DCU1 Network Port Device Paths
DCU2 Network Port Device Paths
DCU3 Network Port Device Paths
Understanding Configuration Guidelines
Understanding System Administration Resources
Understanding Platform-Specific Oracle ILOM Features
SPARC: Server-Specific and New Oracle ILOM Features and Requirements
Unsupported Oracle OS Features
Unsupported Oracle ILOM Features
Oracle VM Server for SPARC Overview
Multipathing Software Overview
Oracle ILOM Remote System Console Plus Overview
Oracle Hardware Management Pack Overview
Oracle Enterprise Manager Ops Center
Time Synchronization and NTP Service
Multi-Domain Extensions to ILOM MIBs
Establish a Network Management Connection to Oracle ILOM
Log In to Oracle ILOM (Web Interface)
Logging In to Oracle ILOM (CLI)
Switch Between the Oracle ILOM CLI and the System Console on a Host
Connect to a PDomain When the System Is Unconfigured and Powered Off
Connect to a PDomain When the Oracle Solaris OS Is Running
Connect to a PDomain When the Oracle Solaris OS Is Unresponsive
Get to the ok Prompt When the Host Is Powered On (Web Interface)
Connect to an LDoms Guest Domain
Connect to Oracle ILOM Remote System Console Plus
Enable Video Redirection From the Oracle Solaris OS
Configure Multiple Display Devices
Reestablish KVMS Connection to SPPs After a Reboot
Controlling the Server, Domains, and Devices
Resetting the Server, SP, or Domains
Reset the Server (Oracle Solaris)
Resetting the SP Configuration
Managing the Server's Boot Behavior
Change the Default Boot Device (ok Prompt)
Create an OpenBoot Boot Path to a Boot Disk
Enable or Disable Automatic Booting (ok Prompt)
SPARC: OpenBoot Boot Configuration Parameters
Booting and Shutting Down the OS
Manually Boot the OS (ok Prompt)
Configuring Oracle ILOM User Accounts and Roles
Understanding Platform and Host-Specific User Role Assignments
Configuring User Accounts (SNMP)
Configuring Host Groups to Authenticate User Accounts (CLI)
Configuring Host Groups to Authenticate User Accounts (SNMP)
Record Network Parameter Values
Viewing the Network Configuration
View Configuration Details for the Network
View Configuration Details for SPs and Hosts
Determine Which SP Is the Active SP
Change the Current Role of the SP Pair
Disable or Re-Enable Network Access to an SP or Host
Determine Current DCU Assignment
Migrate DCUs to a New PDomain (CLI)
Administering CMUs, CMPs, and DIMMs
Display Summary of Installed CMUs
Administering IOUs and PCIe Device Root Complexes
Manage I/O Path Reconfiguration Settings
Identify the Root Complex of a Device
Identifying Domain-Level Commands
PDomain Configuration and Monitoring Commands
Single Sign-On Service Network Deployment Commands
Dedicated SP Interconnect Property Commands
FMA Fault Proxying and Reserved Root Complexes
Virtual Keyswitch Property Commands
Locate the Server (Web Interface)
Obtain the Server Serial Number
Viewing Server and Component Information
Viewing System-Level Information
Viewing Individual Component Properties
XSCF and Oracle ILOM Command Comparison
Identifying SP Configuration and Administration Commands
User Account Administration Commands
Network Configuration/Administration Commands
Supported CMU configurations within a single DCU are as follows:
All four CMUs are installed: rKVMS is supported with redundant paths, all PCIe and EMS slots are accessible, and CMUs are redundant.
Only the first and second CMUs installed: rKVMS is supported and Bounded PDomains have redundant rKVMS paths. If any CMP fails in a Bounded PDomain, the rKVMS connection remains. PCIe slots 9–16 and EMS slots 3–4 are inaccessible. There is no CMU redundancy, so if either CMU fails, the DCU cannot access the SSBs.
Only the first and fourth CMUs installed: rKVMS is supported with no redundancy. If the CMU in the first slot fails, the rKVMS connection is lost. All PCIe and EMS slots are accessible, but if one CMU fails, half of the slots will be disabled. There is no CMU redundancy, so if either CMU fails, the DCU cannot access the SSBs.
Only the second and third CMUs installed: rKVMS is supported with no redundancy. If the CMU in the second slot fails, the rKVMS connection is lost. All PCIe and EMS slots are accessible, but if one CMU fails, half of the slots will be disabled. There is no CMU redundancy, so if either CMU fails, the DCU cannot access the SSBs.
Only the third and fourth CMUs installed: rKVMS is not supported. PCIe slots 1–8 and EMS slots 1–2 are inaccessible. There is no CMU redundancy, so if either CMU fails, the DCU cannot access the SSBs.
Three CMUs installed in any order: rKVMS is supported and all PCIe and EMS slots are accessible. Only one CMU pair and half of the PCIe and EMS slots are redundant. rKVMS is redundant when CMUs are installed in the first and second slots.
Configurations with only the first and third CMUs installed or only the second and fourth CMUs installed are not supported.
A single DCU in a non-Bounded PDomain must have at least two functioning CMUs (one even numbered and one odd numbered) to access the SSBs.
In configurations where a DCU has only two CMUs, individual CMPs can be unconfigured. In configurations where a DCU has three or four CMUs, an entire CMU will be unconfigured if a CMP needs to be reconfigured.
A Bounded PDomain can have only one DCU assigned to it and can have a minimum of one CMP.
When a CMP or CMU fails, or when a CMU is removed, the primary root complexes on that CMP or CMU will no longer be available. For guidelines about setting the Oracle ILOM ioreconfigure property on the PDomain host, see PCIe Device Root Complex Failover Behavior.
Do not assign root complexes pci_1, pci_17, pci_33, and pci_49 to non-primary domains. The four root complexes must always be available to the control domain. See FMA Fault Proxying and Reserved Root Complexes for details.
Do not assign an empty DCU to a PDomain. If the system selects the SPP for the empty DCU to be the PDomain SPP, the DCU to SP interconnect will fail. See FMA Fault Proxying and Reserved Root Complexes for details.
Do not mix SPARC M5 CMUs and SPARC M6 CMUs within the same DCU. A DCU must only contain the same CMU version.