Skip to main content

Contents

  1. Preface
  2. Chapter 1 Understanding an Overview of the SPARC M12/M10
    1.  1.1 Basics of the SPARC M12/M10
    2. Click 1.2 Basics of the XSCF Firmware
    3. Click 1.3 Network Configuration
    4.  1.4 Basics of Hypervisor
    5.  1.5 Basics of Oracle VM Server for SPARC
    6.  1.6 Basics of OpenBoot PROM
  3. Chapter 2 Logging In/Out of the XSCF
    1. Click 2.1 Connecting the System Management Terminal
    2. Click 2.2 Logging In to the XSCF Shell
    3.  2.3 Logging Out from the XSCF Shell
    4. Click 2.4 Logging In to XSCF Web
    5.  2.5 Logging Out From XSCF Web
    6.  2.6 Number of Connectable Users
  4. Chapter 3 Configuring the System
    1. Click 3.1 Preliminary Work for XSCF Setup
    2. Click 3.2 Understanding the Contents of the XSCF Firmware Settings
    3.  3.3 Setting Up From the XSCF Shell
    4.  3.4 Setting Up From XSCF Web
    5. Click 3.5 Creating/Managing XSCF Users
    6. Click 3.6 Setting the XSCF Time/Date
    7. Click 3.7 Configuring the SSH/Telnet Service for Login to the XSCF
    8. Click 3.8 Configuring the HTTPS Service for Login to the XSCF
    9. Click 3.9 Configuring the XSCF Network
    10. Click 3.10 Configuring Auditing to Strengthen XSCF Security
  5. Chapter 4 Configuring the System to Suit the Usage Type
    1. Click 4.1 Setting/Checking the System Altitude
    2. Click 4.2 Controlling System Start
    3. Click 4.3 Enabling/Disabling Dual Power Feed
    4. Click 4.4 Reducing Power Consumption
    5. Click 4.5 Connecting a DVD Drive
    6. Click 4.6 Using Remote Storage
  6. Chapter 5 CPU Activation
    1.  5.1 Basic Concepts of CPU Activation
    2.  5.2 CPU Activation Key
    3. Click 5.3 Adding CPU Core Resources
    4. Click 5.4 Deleting CPU Core Resources
    5. Click 5.5 Moving CPU Core Resources
    6. Click 5.6 Displaying CPU Activation Information
    7. Click 5.7 Saving/Restoring CPU Activation Keys
    8. Click 5.8 Troubleshooting CPU Activation Errors
    9.  5.9 Important Notes about CPU Activation
  7. Chapter 6 Starting/Stopping the System
    1. Click 6.1 Starting the System
    2. Click 6.2 Stopping the System
    3.  6.3 Rebooting the System
    4.  6.4 Suppressing Starting Oracle Solaris at Power-on
  8. Chapter 7 Controlling Physical Partitions
    1.  7.1 Configuring a Physical Partition
    2. Click 7.2 Setting the Physical Partition Operation Mode
    3.  7.3 Powering On a Physical Partition
    4.  7.4 Powering Off a Physical Partition
    5.  7.5 Changing the Configuration of a Physical Partition
  9. Chapter 8 Controlling Logical Domains
    1.  8.1 Configuring a Logical Domain
    2. Click 8.2 Configuring the Oracle Solaris Kernel Zone
    3. Click 8.3 Switching to the Control Domain Console From the XSCF Shell
    4. Click 8.4 Returning to the XSCF Shell From the Control Domain Console
    5.  8.5 Starting a Logical Domain
    6.  8.6 Shutting Down a Logical Domain
    7. Click 8.7 Ordered Shutdown of Logical Domains
    8.  8.8 Checking CPU Activation Information
    9. Click 8.9 Setting the OpenBoot PROM Environment Variables of the Control Domain
    10. Click 8.10 Domain Console Logging Function
    11.  8.11 Changing the Configuration of a Logical Domain
    12.  8.12 Setting the Logical Domain Time
    13. Click 8.13 Collecting a Hypervisor Dump File
    14. Click 8.14 Managing Logical Domain Resources Associated with CPU Sockets
    15. Click 8.15 Setting the Physical Partition Dynamic Reconfiguration Policy
    16. Click 8.16 Setting the Maximum Page Size of a Logical Domain
  10. Chapter 9 Managing the Systems Daily
  11. Chapter 10 Preparing/Taking Action for Failures
    1.  10.1 Learning about Troubleshooting and Related Functions
    2. Click 10.2 Receiving Notification by E-mail When a Failure Occurs
    3. Click 10.3 Monitoring/Managing the System Status With the SNMP Agent
    4. Click 10.4 Monitoring the System
    5.  10.5 Understanding the Failure Degradation Mechanism
    6. Click 10.6 Checking Failed Hardware Resources
    7. Click 10.7 Setting Automatic Replacement of Failed CPU Cores
    8.  10.8 Setting Recovery Mode
    9.  10.9 Setting Up a Redundant Component Configuration
    10. Click 10.10 Saving/Restoring XSCF Settings Information
    11. Click 10.11 Saving/Restoring Logical Domain Configuration Information in the XSCF
    12. Click 10.12 Saving/Restoring Logical Domain Configuration Information in an XML File
    13. Click 10.13 Saving/Restoring the OpenBoot PROM Environment Variables
    14.  10.14 Saving/Restoring the Contents of a Hard Disk
    15.  10.15 Resetting a Logical Domain
    16. Click 10.16 Causing a Panic in a Logical Domain
    17.  10.17 Resetting a Physical Partition
    18. Click 10.18 Returning the Server to the State at Factory Shipment
    19.  10.19 Collecting a Crash Dump File Using Deferred Dump
  12. Chapter 11 Checking the System Status
    1. Click 11.1 Checking the System Configuration/Status
    2. Click 11.2 Checking a Physical Partition
  13. Chapter 12 Checking Logs and Messages
    1. Click 12.1 Checking a Log Saved by the XSCF
    2. Click 12.2 Checking Warning and Notification Messages
  14. Chapter 13 Switching to Locked Mode/Service Mode
    1.  13.1 Understanding the Differences Between Locked Mode and Service Mode
    2.  13.2 Switching the Operating Mode
  15. Chapter 14 Configuring a Highly Reliable System
    1. Click 14.1 Configuring Memory Mirroring
    2. Click 14.2 Configuring Hardware RAID
    3.  14.3 Using the LDAP Service
    4.  14.4 Using SAN Boot
    5.  14.5 Using iSCSI
    6. Click 14.6 Remote Power Management for the SPARC M12/M10 and I/O Devices
    7.  14.7 Using an Uninterruptible Power Supply
    8. Click 14.8 Using Verified Boot
  16. Chapter 15 Expanding the System Configuration
    1.  15.1 Changing the Virtual CPU Configuration
    2.  15.2 Changing the Memory Configuration
    3. Click 15.3 Dynamic Reconfiguration Function for PCIe Endpoint Devices
    4. Click 15.4 Using the PCI Expansion Unit
    5.  15.5 Expanding the SPARC M12-2S/M10-4S
  17. Chapter 16 Updating the XCP Firmware
    1. Click 16.1 Basics of Firmware Update
    2. Click 16.2 Before Updating Firmware
    3.  16.3 Update Flow
    4.  16.4 Preparing an XCP Image File
    5. Click 16.5 Updating Firmware
    6.  16.6 Updating Firmware From XSCF Web
    7. Click 16.7 Firmware Version Matching with Parts Addition/Replacement
    8.  16.8 Trouble During Firmware Update
    9.  16.9 FAQ Relating to Firmware Update
  18. Chapter 17 Updating Oracle Solaris and Oracle VM Server for SPARC
  19. Chapter 18 Troubleshooting
    1.  18.1 Troubleshooting for the XSCF
    2.  18.2 Precautions Concerning Using the RESET Switch
    3.  18.3 Frequently Asked Questions / FAQ
    4.  18.4 System Troubleshooting With the XSCF
  20. Appendix A Lists of SPARC M12/M10 System Device Paths
    1.  A.1 SPARC M12-1 Device Paths
    2. Click A.2 SPARC M12-2 Device Paths
    3. Click A.3 SPARC M12-2S Device Paths
    4.  A.4 SPARC M10-1 Device Paths
    5. Click A.5 SPARC M10-4 Device Paths
    6. Click A.6 SPARC M10-4S Device Paths
  21. Appendix B Identifying an SAS2 Device Based on a WWN
    1.  B.1 World Wide Name (WWN) Syntax
    2.  B.2 Overview of probe-scsi-all Command Output
    3. Click B.3 Identifying a Disk Slot by Using the probe-scsi-all Command
    4. Click B.4 Identifying Disk Slot
  22. Appendix C List of the XSCF Web Pages
    1.  C.1 Overview of the Pages
    2.  C.2 Understanding the Menu Configuration
    3. Click C.3 Available Pages
  23. Appendix D XSCF MIB Information
    1.  D.1 MIB Object Identification
    2.  D.2 Standard MIB
    3. Click D.3 Extended MIB
    4.  D.4 Traps
  24. Appendix E SPARC M12/M10 System-specific Functions of Oracle VM Server for SPARC
    1.  E.1 Ordered Shutdown of Logical Domains
    2.  E.2 CPU Activation Support
    3. Click E.3 Checking Failed Resources
    4.  E.4 Automatic Replacement of Failed CPUs
    5.  E.5 Hypervisor Dump
    6.  E.6 Domain Console Logging Function
    7.  E.7 CPU Socket Restrictions
  25. Appendix F SAS2IRCU Utility Command Examples
    1.  F.1 Displaying a List of SAS Controllers Recognized by sas2ircu
    2.  F.2 Displaying the Information of a Hardware RAID Volume
    3.  F.3 Adding a Hardware RAID Volume
    4.  F.4 Displaying the Configuration Status of a Hardware RAID Volume
    5.  F.5 Creating a Hot Spare of a Hardware RAID Volume
    6.  F.6 Deleting a Hot Spare of a Hardware RAID Volume
    7.  F.7 Deleting a Hardware RAID Volume
    8.  F.8 Identifying the Faulty Disk Drive of a Hardware RAID Volume
  26. Appendix G SPARC M12-1/M10-1 XSCF Startup Mode Function
    1. Click G.1 Function Overview
    2. Click G.2 Restrictions and Notes
    3.  G.3 Configuration Procedure
  27. Appendix H OpenBoot PROM Environment Variables and Commands
    1.  H.1 SCSI Device Display
    2.  H.2 Unsupported OpenBoot PROM Environment Variables
    3.  H.3 Unsupported OpenBoot PROM Commands
    4.  H.4 Behavior With the Security Mode Enabled
  28. Appendix I How to Specify the Boot Device
    1.  I.1 Device Path of the Internal Storage
    2.  I.2 Method of Specification With a PHY Number
    3.  I.3 Method of Specification With a Target ID
    4.  I.4 Method of Specification With an SAS Address
    5.  I.5 Method of Specification With a Volume Device Name
    6.  I.6 Notes About the Device Alias net of the SPARC M12 Without On-Board LAN
  29. Appendix J Lists of DVD Drive Aliases
    1. Click J.1 External DVD Drive Aliases
    2. Click J.2 Remote Storage DVD Drive Aliases
  30. Appendix K CPU Activation Interim Permit
    1.  K.1 What is the CPU Activation Interim Permit?
    2.  K.2 Terms of Use of the CPU Activation Interim Permit and Precautions
    3. Click K.3 Related Commands
    4. Click K.4 Flows and Procedures for Using a CPU Activation Interim Permit
    5. Click K.5 Event Notification of the CPU Activation Interim Permit
    6. Click K.6 Other Important Notes

1.1 Basics of the SPARC M12/M10


1.1 Basics of the SPARC M12/M10
This section provides an overview of the SPARC M12/M10 systems.

The SPARC M12/M10 is a UNIX server system that uses the SPARC processor and Oracle Solaris. CPU Activation allows the expansion of resources in units of one core in phases. The SPARC M12-2S/M10-4S uses a building block system so that the system can be configured as appropriate for the intended business use and the scale of business. The servers can be applied in many ways; as the database servers best-suited for data centers in an era of cloud computing, and as the Web servers or application servers for which high throughput is demanded.

The following models have been prepared to support various intended uses.
  1. SPARC M12-1
    This 1-CPU compact model with six cores at maximum is designed for space saving and high performance.
  2. SPARC M12-2
    This model consists of up to two CPUs, each of which has up to 12 cores.
  3. SPARC M12-2S
    This model consists of up to two CPUs, each of which has up to 12 cores. With the building block (BB) system, the number of connected SPARC M12-2S units can be adjusted according to the performance required. A configuration can be expanded to up to four BBs by connecting the SPARC M12-2S units directly to one another. Moreover, a system that uses crossbar boxes supports a configuration of up to 16 BBs and scales up to 32 CPUs--the scalability is ensured.
  4. SPARC M10-1
    This 1-CPU compact model with 16 cores at maximum is designed for space saving and high performance.
  5. SPARC M10-4
    This model consists of up to four CPUs, each of which has up to 16 cores.
  6. SPARC M10-4S
    This model consists of up to four CPUs, each of which has up to 16 cores. With the building block (BB) system, the number of connected SPARC M10-4S units can be adjusted according to the performance required. A configuration can be expanded to up to four BBs by connecting the SPARC M10-4S units directly to one another. Moreover, a system that uses crossbar boxes supports a configuration of up to 16 BBs and scales up to 64 CPUs--the scalability is ensured.
Note - If the building block system is used, the SPARC M12-2S and SPARC M10-4S cannot be mixed in the same configuration.
System configuration
This section describes the system configuration.

Figure 1-1 shows an example of a system configuration where more than one SPARC M12-2S or more than one SPARC M10-4S is connected by the building block system. A single SPARC M12-2S/M10-4S unit that can have a building block configuration is one building block. A physical partition (PPAR) is configured by combining one or more building blocks.
Figure 1-2 shows an example of a system configuration of SPARC M12-1/M12-2/M10-1/M10-4. A single SPARC M12-1/M12-2/M10-1/M10-4 unit cannot have a building block configuration yet it is sometimes called a physical partition. Note that the SPARC M12-2S and SPARC M10-4S in a single unit configuration is also sometimes called a physical partition.
Figure 1-1  Example of a SPARC M12-2S/M10-4S System Configuration
Figure 1-1 Example of a SPARC M12-2S/M10-4S System Configuration
Figure 1-2  Example of a SPARC M12-1/M12-2/M10-1/M10-4 System Configuration
Figure 1-2 Example of a SPARC M12-1/M12-2/M10-1/M10-4 System Configuration
The following sections describe "physical partitions" and "logical domains," which are key to the system configuration.
Configuration of Physical Partitions
To configure a SPARC M12-2S or SPARC M10-4S system, configure a physical partition (PPAR) by combining one or more building blocks of the same model. Configuring physical partitions is called partitioning, and the resulting configured object is called a physical partition (PPAR). Physical partitions are configured using the XSCF firmware, which is the system management firmware.
In the example shown in Figure 1-1, PPAR#00 is one of the building blocks (BBs), and BB#00 is configured as the physical partition PPAR#00. Similarly, physical partition PPAR#01 is configured from BB#01, BB#02, and BB#03.
Once a physical partition is configured, hardware resources on the physical partition are assigned to logical domains.
Note that since the SPARC M12-1/M12-2/M10-1/M10-4 is a model consisting of a single unit, it can be configured with only one physical partition.
Configuration of Logical Domains
A physical partition has the CPUs, memory, I/O devices, and other hardware resources to be assigned to logical domains. A logical domain is configured using the Oracle VM Server for SPARC software.
A configured logical domain is handled as one UNIX system on the software side. Oracle Solaris and applications can be installed in logical domains and applied to tasks separately. In the example shown in Figure 1-1, the logical domains primary, ldom00, and ldom01 are configured with the assignment of hardware resources of the physical partition PPAR#00.
Similarly, the logical domains primary, ldom10, ldom11, and ldom12 are configured with the physical partition PPAR#01.
One of the logical domains, to which physical partition resources are assigned, serves as the domain controlling all the logical domains. It is called the control domain. The control domain, which is the logical domain controller, also serves to handle communication between the physical partition and logical domains.
Firmware/Software Required for the Systems
The physical partitions are implemented with the XSCF firmware and the logical domain, Oracle VM Server for SPARC. Even for a configuration of only the control domain, Oracle VM Server for SPARC is required.
Between the XSCF firmware and Oracle VM Server for SPARC, communication for monitoring and managing the whole system is handled inside the system. Users do not need to pay attention to that.
The interface between the XSCF firmware and Oracle VM Server for SPARC in the SPARC M12/M10 systems is implemented by firmware named Hypervisor.
"1.2 Basics of the XSCF Firmware" and subsequent sections describe firmware and software used in the systems.

Top of Page