Skip to main content

Contents

  1. Preface
  2. Chapter 1 Understanding an Overview of Domain Configuration
    1. Click 1.1 SPARC M12/M10 Domain Configurations
    2.  1.2 SPARC M12/M10 Hardware Resources
    3. Click 1.3 What is a Physical Partition?
    4. Click 1.4 What is a Logical Domain?
    5. Click 1.5 What is Physical Partition Dynamic Reconfiguration?
    6. Click 1.6 Mixed Use of the SPARC64 X+ Processor and SPARC64 X Processor
  3. Chapter 2 Conditions and Settings for System Operation
    1. Click 2.1 XSCF Status Management
    2. Click 2.2 XSCF Conditions and Settings
    3. Click 2.3 Oracle Solaris Conditions and Settings
    4. Click 2.4 Logical Domain Conditions and Settings
    5. Click 2.5 Dynamic Reconfiguration Conditions and Settings
    6. Click 2.6 Considerations When Using the SPARC64 X+ Processor
  4. Chapter 3 Operations for Domain Configuration
    1. Click 3.1 Operations and Commands Related to Physical Partition Configurations
    2. Click 3.2 Operations and Commands Related to Logical Domain Configurations
  5. Chapter 4 Configuring a Physical Partition
    1.  4.1 Physical Partition Configuration Flow
    2.  4.2 Configuring and Operating a Physical Partition
  6. Chapter 5 Logical Domain Configuration Example
    1.  5.1 Logical Domain Configuration Flow
    2. Click 5.2 Example of Logical Domain Configuration Operations
  7. Chapter 6 Physical Partition Reconfiguration
    1. Click 6.1 Flow for Physical Partition Reconfiguration
    2. Click 6.2 Example of System Board Addition
    3. Click 6.3 Example of Operations for Deleting a System Board
    4.  6.4 Example of Operations for Moving a System Board
    5.  6.5 Example of Operations for Replacing a System Board
    6.  6.6 Considerations When Changing a Physical Partition Number
  8. Chapter 7 Migrating a Guest Domain
    1. Click 7.1 Overview
    2.  7.2 Migrating a Guest Domain
    3.  7.3 Guest Domain Migration Example
  9. Appendix A Environment Configuration Examples and Procedures Using Physical Partition Dynamic Reconfiguration
    1. Click A.1 Updating a System That Does Not Support Physical Partition Dynamic Reconfiguration to One That Does Support It
    2. Click A.2 For New Installations from XCP 2220 or Later, Where the Logical Domain Configuration Has No Free Space for Hardware Resources
    3. Click A.3 For New Installations from XCP 2220 or Later, Where the Logical Domain Configuration Has Free Hardware Resources
    4. Click A.4 For Expansion of a Newly Installed System of Version XCP 2220 or Later from the 1BB to 2BB Configuration
    5. Click A.5 For Installation of the System Board Configured by the SPARC64 X+ Processor to the Physical Partition Configured Only by the SPARC64 X Processor
    6. Click A.6 For Active Replacement of a System Board in a Configuration with Only the Control Domain (for Oracle VM Server for SPARC 3.2 or Later)
  10. Appendix B Supplementary Information for Using Dynamic Reconfiguration
    1. Click B.1 Considerations for the XSCF Reboot or Failover Time
    2.  B.2 Supplementary Information on CPU Operational Mode
    3.  B.3 Other Considerations
  11. Appendix C Meanings of Messages and Corresponding Corrective Action
    1. Click C.1 Command Messages

2.2.2 Settings From the XSCF


2.2.2 Settings From the XSCF
Physical partition configuration-related functions include several optional functions for reconfiguring a physical partition more smoothly and continuing operation. The functions prevent complexities regarding Oracle Solaris reconfiguration, memory allocation, etc. Use the XSCF shell or XSCF Web to configure these optional functions. This section describes the following optional functions:
  1. Configuration policy option
  2. Memory nullification option
  3. I/O nullification option
Use the setpcl command to set these options.
Setting the configuration policy option
When a physical partition is powered on or a system board (PSB<BB>) is added with physical partition dynamic reconfiguration, the hardware is subject to a power-on self-test to ensure safe insertion of the PSB (BB). The configuration policy is an option that specifies the degradation range that is applied if an error is detected by these power-on self-tests.

You can set the unit of degradation as the following: the part where the hardware error is detected, the system board (PSB) unit (BB unit) where that part is mounted, or the physical partition. Table 2-3 lists the values and the units of degradation that can be set for this option. The default for this option is "fru."
Table 2-3  Unit of Degradation
Setting Value Unit of Degradation
fru Degradation is performed in units of parts, such as a CPU or memory.
psb Degradation is performed in system board (PSB) by units (BB units).
system The unit of degradation is the physical partition. The physical partition is stopped without degradation.
Note - Stop the relevant physical partition before setting the configuration policy option.
Memory nullification option
This option prevents the memory on a system board (PSB<BB>) to be incorporated into a physical partition from being used in logical domains. You can use this option in combination with the I/O nullification option to incorporate only the CPUs on a system board added to the target physical partition, into logical domains without incorporating the memory into the logical domains. You can select either "true" or "false" for this option. The former enables memory nullification, and the latter disables it. The default is "false."
Note - Even with the memory nullification option enabled, you need to actually load memory to diagnose and manage the PSB (BB). The memory available in the physical partition decreases and performance may deteriorate when the memory nullification option is enabled. You need to consider the impact on business before setting this option.
Note - Set the memory nullification option when the relevant PSB (BB) is in the system board pool state or when the physical partition power is off.
I/O nullification option
This option prevents the PCI card, disk drive, and basic local area network (LAN) port on a system board (PSB<BB>) and PCI expansion unit from being inserted into the target physical partition. If only the CPUs and memory on the PSB (BB) need to be used in the physical partition, specify "true" to enable the I/O nullification option. If the PCI card and I/O device of the PSB (BB) need to be used in the physical partition, set this option to "false." In this case, you need to fully understand the restrictions on using these I/O devices. You also need to stop any software (e.g., application program or daemon) and I/O domains that use the I/O devices before deleting the PSB (BB) with dynamic reconfiguration.

If the physical partition is started with the logical domain configuration information configured to the factory-default settings, it is started according to the setting of the I/O nullification option. Suppose that the physical partition is started with logical domain configuration information other than the factory-default settings, and that the root complex and the I/O devices of the relevant system board belong to any one of the logical domains. The system determines that the physical partition configuration has been changed and starts the physical partition by switching to the factory-default settings. If the above does not belong to any of the logical domains, switching to the factory-default settings is not performed. If the PSB (BB) is added by means of dynamic reconfiguration, insertion processing is performed for the physical partition according to the settings made for the I/O nullification.

The default setting for the I/O nullification option is "false."
Note - Set the I/O nullification option when the relevant PSB (BB) is in the system board pool state or when the physical partition power is off.

Top of Page