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

K.4.2 Flow and Procedure for XCP 232x


K.4.2 Flow and Procedure for XCP 232x
With XCP 232x, a CPU Activation Interim Permit can be used only for a SPARC M10-1/M10-4 system.
Operation flow for XCP 232x
The operation flow is as follows.
  1. Realize that additional CPU cores are required, and start the process of purchasing required CPU Activation keys.
  1. Enable a CPU Activation Interim Permit.
  1. Register the obtained CPU Activation keys with the system.
  1. Disable the CPU Activation Interim Permit.
Configuration Example
The description in "Operation Procedure for XCP 232x" uses the following configuration as an example.
  1. Single CPU socket SPARC M10-1 with 16 physical CPU cores is used.
  1. CPU Activations to activate 4 CPU cores have been purchased and registered in the system.
  1. The system consists of two logical domains and they are running.
  1. - Two CPU cores are assigned to the control domain (primary domain).
  1. - Two CPU cores are assigned to the guest domain (dm0).
  1. - To respond to a load increase, the guest domain (dm0) requires six more CPU cores.
Figure K-2  Configuration Example for XCP 232x (SPARC M10-1)
Figure K-2 Configuration Example for XCP 232x (SPARC M10-1)
Note - CPU Activation keys registered in the system enable a definite number of CPU cores. They do not enable CPU cores by specifying the CPU socket and physical location of each CPU core. For the purpose of easy understanding, specific CPU cores are enabled and assigned to the logical domains in Figure K-2.
Operation Procedure for XCP 232x
The operation procedure is as follows.
  1. Confirm that additional CPU cores are required, and start the process of purchasing required CPU Activation keys.
  1. Confirm the following before starting the purchase process.
  1. a. Determine whether additional CPU cores are required based on a load analysis or estimate that you perform for the system.
  1. b. A CPU Activation Interim Permit can be used for 30 days. We recommend confirming in advance how many days it will take for you to receive CPU Activation keys in your region. For this information, contact your local sales representative.
  1. Enable a CPU Activation Interim Permit.
    Perform the following.
  1. a. Execute the showcodusage command of the XSCF to check the current usage of the CPU cores of the system.
XSCF> showcodusage -p resource
Resource In Use Installed CoD Permitted Status
-------- ------ --------- ------------- ------

PROC 4 16 4 OK: 0 cores available
  1. Table K-5 lists the meanings of values displayed by the showcodusage command.
Table K-5  Meanings of showcodusage
Column Display Description Meaning of Values of Command Example
In Use Number of CPU cores currently used in the logical domains of the entire system out of available CPU cores in the case where they are managed through the number of purchased CPU Activations "4": 4 CPU cores are currently used in the logical domains of the entire system.
Installed Number of physical CPU cores mounted on the entire system "16": 16 physical CPU cores are mounted on the entire system.
CoD Permitted Number of CPU Activations purchased and registered in the system 4: CPU Activations to activate 4 CPU cores are assigned to the system.
Status Number of CPU Activations that are not currently used in the logical domains of the system (difference between "CoD Permitted" and "In Use") "OK": The value obtained by subtracting the value of "In Use" from the value of "CoD Permitted" is 0 or greater, which means no violation.
Reference - "VIOLATION": The value obtained by subtracting the value of "In Use" from the value of "CoD Permitted" is less than 0, which means a violation.
Unused- Assigned Number of CPU Activations that are not currently used in the logical domains of the system. A negative value indicates that the number of CPU cores that are currently used in violation. "0": CPU cores corresponding to the number of CPU Activations assigned to the system are currently used.
Reference - "-12": 12 more CPU cores than the number of assigned CPU Activations are currently used, which means a violation.
  1. If the value of "Installed" is equal to that of "CoD Permitted," then it indicates that CPU Activation keys for all physically incorporated CPU cores have been registered. In this case, the CPU Activation Interim Permit is not required. Do not enable the function.
  1. b. Execute the setinterimpermit command of the XSCF to enable the CPU Activation Interim Permit. All CPU cores in CPU chips mounted on the system are made available by executing this command.
XSCF> setinterimpermit -p 0 -c enable
Note:
Interim Permit can be used only once.
Please add CPU activation(s) within 30 days of enabling the Interim Permit.

The Interim Permit for the PPAR will be changed to enabled.
Continue?[y|n] :y

Completed.
  1. c. Execute the showcodusage command of the XSCF to check the number of additional CPU cores that are made available.
XSCF> showcodusage -p resource
Resource In Use Installed CoD Permitted Status
-------- ------ --------- ------------- ------

PROC 4 16 4 OK: 0 cores available
  1. This example shows that "Installed" is "16". The value did not change between before and after the CPU Activation Interim Permit was enabled. However, it shows that 12 additional CPU cores have been made available by enabling the CPU Activation Interim Permit. In this case, up to 12 additional CPU cores can be used in the logical domain (dm0) for 30 days.
  1. Rather than using all the additional CPU cores that have been made available, only assign CPU cores corresponding to the number of CPU Activations you plan to purchase to logical domains.
  1. For example, if you want to purchase and add two CPU cores, we strongly recommend assigning only two additional CPU cores to logical domains. If you assign four CPU cores to logical domains and then purchase a CPU Activation to activate only two additional CPU cores, the total will be reduced by two CPU cores. This may cause a performance problem after you disable a CPU Activation Interim Permit.
  1. d. If you execute the showcodusage command of the XSCF without options at this point, the following output appears.
XSCF> showcodusage
Resource In Use Installed CoD Permitted Status
-------- ------ --------- ------------- ------

PROC 4 16 4 OK: 0 cores available
PPAR-ID/Resource In Use Installed Assigned
---------------- ------ --------- --------------

0 - PROC 4 16 4 cores
Unused - PROC 0 0 0 cores
  1. Note that, if you execute the showdusage command of the XSCF at this point, the display content does not change between before and after enabling the CPU Activation Interim Permit, even though the number of available CPU cores has increased through the use of the function.
  1. The showcodusage command is used to manage the number of CPU cores currently used in logical domains and the number of registered (purchased) CPU Activations. Therefore, the content displayed by the showcodusage command is not affected by whether a CPU Activation Interim Permit is enabled/disabled. The "CoD Permitted" field, which is for the number of purchased and registered CPU Activations, and "In Use," which is for the number of CPU cores used in logical domains, display the current values as they are.
  1. In this example, no additional CPU cores have been assigned to the logical domains yet. The value of "CoD Permitted," which shows the number of CPU Activations registered in the system, is "4" and the value of "Installed," which shows the number of physical CPU cores, is "16". This means that there is a lack of CPU Activations for 12 physical CPU cores. However, the 12 CPU cores can be used for 30 days because CPU Activation Interim Permit is enabled.
  1. If, for example, you assign the 12 CPU cores to logical domains while the CPU Activation Interim Permit is enabled, "Status" displays "VIOLATION: 12 cores in excess." In this case, "VIOLATION" does not indicate urgency. It alerts that a CPU Activation violation will occur when the CPU Activation Interim Permit expires or is disabled.
  1. In the "Assigned" field of the "Unused" row, you can confirm the number of CPU cores that have not yet been used in the logical domains of the system against the purchased CPU Activations. These unused CPU cores are used by the CPU automatic replacement function in the event of a failure of a CPU core in use.
  1. e. Execute the showinterimpermit command of the XSCF to confirm the status of the CPU Activation Interim Permit. The following example shows that the CPU Activation Interim Permit is enabled and there are 29 days left before the expiration.
XSCF> showinterimpermit -p 0
Interim permit for PPAR 0: enabled [29 days remaining]
  1. f. To start using additional CPU cores in one or more logical domains, execute the ldm add-core command from the control domain (primary domain). The following example shows that six CPU cores are added to the logical domain.
# ldm add-core 6 dm0
  1. g. Execute the showcodusage command of the XSCF.
    The following example shows that the value of "In Use" increased from "4" to "10" because six CPU cores were added and used in the logical domains. Since the difference between "In Use" and "CoD Permitted" is six, "VIOLATION: 6 cores in excess" is displayed, which means that six CPU cores are temporarily in violation. As mentioned above, this "VIOLATION" does not indicate urgency.
XSCF> showcodusage -p resource
Resource In Use Installed CoD Permitted Status
-------- ------ --------- ------------- ------

PROC 10 16 4 VIOLATION: 6 cores in excess
Note - It takes up to 20 minutes to reflect information on the CPU core usage of logical domains. Therefore, the showcodusage command may not display the change as a result of the use of the ldm command for up to 20 minutes.
  1. h. If you want to confirm the number of CPU cores used in logical domains immediately after changing the assignment of CPU cores, execute the ldm list-permits command from the control domain.
# ldm list-permits
  1. i. If the CPU Activation Interim Permit is enabled while all logical domains are powered off, the ldm command may not be required for adding CPU cores to the logical domains.
  1. If executing the showdomainconfig command of the XSCF displays "factory-default" in "Booting config" as shown below, all available CPU cores will be automatically used in the control domain (primary domain) the next time the domain is powered on. This is because, in the case of the control domain ("factory-default"), all available hardware resources are assigned to the domain when the power is turned on.
XSCF> showdomainconfig -p 0
PPAR-ID :0
Booting config
(Current) :factory-default
(Next) :factory-default
  1. If "Booting config" is not "factory-default", execute the ldm command to assign additional CPU cores after the control domain is booted. After executing the ldm command, save the changed domain configuration information by using the "ldm add-spconfig" command. This ensures that the latest logical domain configuration information is used later when the domain is rebooted.
  1. We strongly recommend using a name different from the currently used one as the logical domain configuration name, as shown in the following example.
XSCF> showdomainconfig -p 0
PPAR-ID :0
Booting config
(Current) :before-IPermit
(Next) :IPermit-enabled
  1. Register the obtained CPU Activation keys with the system.
    Perform the following.
  1. a. After receiving newly purchased CPU Activations, register them with the system by using the addcodactivation command from the XSCF.
XSCF> addcodactivation
Product: SPARC M10-1 SequenceNumber: 1
Cpu: noExpiration 2
Text-Signature-SHA256-RSA2048:
U1VOVyxTUEFSQy1FbnRlcnByaXNlAA........
Above Key will be added, Continue?[y|n]: y
XSCF>
  1. b. Set the number of CPU Activations for the physical partition by using the setcod command.
XSCF> setcod -p 0 -s cpu -c set 10
PROC Permits assigned for PPAR 1 : 4 -> 10
 
PROC Permits assigned for PPAR will be changed.
Continue? [y|n] :y
 
Completed.
  1. c. Confirm the status of CPU cores by using the showcodusage command.
  1. The following example shows that ten CPU cores are available in total because six new CPU Activations are registered and added to four CPU Activations and settings are made for the physical partition.
XSCF> showcodusage -p resource
Resource In Use Installed CoD Permitted Status
-------- ------ --------- ------------- ------

PROC 10 16 10 OK: 0 cores available
  1. d. You will disable the CPU Activation Interim Permit in step 4. Therefore, carefully check that the required number of CPU cores is displayed in "CoD Permitted." The number displayed in the "In Use" field must be equal to or less than that in the "CoD Permitted" field while the domain is running.
    If the number displayed in the "In Use" field is greater than that in the "CoD Permitted" field, the system detects a CPU core violation. For details on system operation when a violation is detected after the CPU Activation Interim Permit expires or is disabled, see "K.4.3 Case Where the Function Has Expired or is Disabled."
  1. Disable the CPU Activation Interim Permit.
  1. Perform the following.
  1. a. Execute the setinterimpermit command from the XSCF to disable the CPU Activation Interim Permit.
XSCF> setinterimpermit -p 0 -c disable
Interim permit will be disabled.
Continue?[y|n] :y

Completed.
  1. b. Execute the showcodusage command to check the current usage of CPU cores.
  1. Confirm that the Status field is OK, which means that all CPU cores in use are permitted to be used through the purchased CPU Activations.
XSCF> showcodusage -p resource
Resource In Use Installed CoD Permitted Status
-------- ------ --------- ------------- ------

PROC 10 16 10 OK: 0 cores available

Top of Page