SPARC Enterprise M4000/M5000/M8000/M9000 Servers Capacity on Demand (COD) User's Guide Manual Code: C120-E336-09EN January 2012, Revision A
Copyright © 2007, 2012, Fujitsu Limited. All rights reserved. Oracle and/or its affiliates provided technical input and review on portions of this material. Oracle and/or its affiliates and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document, and such products, technology and this document are protected by copyright laws, patents, and other intellectual property laws and international treaties.
Copyright © 2007, 2012, Fujitsu Limited. Tous droits réservés. Oracle et/ou ses sociétés affiliées ont fourni et vérifié des données techniques de certaines parties de ce composant. Oracle et/ou ses sociétés affiliées et Fujitsu Limited détiennent et contrôlent chacune des droits de propriété intellectuelle relatifs aux produits et technologies décrits dans ce document.
Contents Preface vii Capacity on Demand (COD) Administration About Capacity on Demand COD Boards 1 1 The COD Hardware Activation Option COD CPU Activation COD Activation Log COD CPU Allocation 2 3 3 4 Notes on Domain Configuration Headroom Management Violations 1 5 5 6 COD Commands 6 Activating COD Resources 8 ▼ To Purchase COD Hardware Activation Options ▼ To Install a COD Key 8 ▼ To Delete a COD Key 9 ▼ To Reserve COD Permits for a Domain ▼ To Enable, Increase, or Decrease Hea
▼ To Display COD Information ▼ To Display COD Activation History ▼ To Display COD Permit Status ▼ To Display Usage Statistics for COD Resources Index vi 12 13 13 15 17 SPARC Enterprise Mx000 Servers Capacity on Demand (COD) User’s Guide • January 2012
Preface This guide describes how to manage system resources with the Capacity on Demand (COD) feature of the SPARC Enterprise M4000/M5000/M8000/M9000 servers. And it includes instructions for ordering and installing your COD Hardware Activation Option. Some references to server names and document names are abbreviated for readability. For example, if you see a reference to the M9000 server, note that the full product name is the SPARC Enterprise M9000 server.
Audience This guide is written for experienced system administrators with working knowledge of computer networks and advanced knowledge of the Oracle Solaris Operating System (Oracle Solaris OS). Related Documentation All documents for your sever are available online at the following locations: Documentation Link Sun Oracle software-related manuals (Oracle Solaris OS, and so on) http://www.oracle.com/documentation Fujitsu documents http://www.fujitsu.
Related SPARC Enterprise M4000/M5000/M8000/M90000 Servers Documents SPARC Enterprise M8000/M9000 Servers Unpacking Guide* SPARC Enterprise M4000/M5000 Servers Installation Guide SPARC Enterprise M8000/M9000 Servers Installation Guide SPARC Enterprise M4000/M5000 Servers Service Manual SPARC Enterprise M8000/M9000 Servers Service Manual External I/O Expansion Unit Installation and Service Manual SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers RCI Build Procedure SPARC Enterprise M3000/M4000/M5000/M80
Text Conventions This manual uses the following fonts and symbols to express specific types of information. Fonts/symbols Meaning Example AaBbCc123 What you type, when contrasted with on-screen computer output. This font represents the example of command input in the frame. XSCF> adduser jsmith AaBbCc123 The names of commands, files, and directories; on-screen computer output. This font represents the example of command output in the frame.
Documentation Feedback If you have any comments or requests regarding this document, go to the following website: http://www.fujitsu.com/global/contact/computing/sparce_index.
xii SPARC Enterprise Mx000 Servers Capacity on Demand (COD) User’s Guide • January 2012
Capacity on Demand (COD) Administration This guide describes how to manage system resources with the Capacity on Demand (COD) feature of the SPARC Enterprise M4000/M5000/M8000/M9000 servers.
COD boards are subject to the same limitations for mixed architectures and CPU speeds as system boards. Likewise, COD board software requirements, such as the Oracle Solaris Operating System (Oracle Solaris OS) or OpenBoot PROM version, are the same as those of system boards. For M8000/M9000 (high-end) servers, you can order COD boards at original purchase or at any time afterward. High-end servers support any combination of COD boards and system boards.
TABLE 1 Type of Usable COD Permits and XCP Version COD Permits Can also be used on other Server-specific servers* XCP 1100 or Earlier XCP 1101 or Later X† S S S * The COD permits for the M4000/M5000 servers cannot be installed on the M8000/M9000 servers, and vice versa. † If you are using XCP 1100 or earlier, each COD permit is assigned to a server’s individual Chassis HostID and cannot be installed on other servers. X: Not supported. S: Supported.
COD CPU Allocation COD CPUs are activated either when a domain with a COD board is powered on or when a new COD board is installed and powered on. The XSCF firmware activates COD CPUs automatically on a first-come, first-served basis. However, you can reserve one or more COD permits for a particular domain. At board power on, the Service Processor determines which COD CPUs are in working order and requests COD permits for them.
When the domains are first powered on, four COD permits are assigned to COD CPUs in domain 0 and two to domain 1. The remaining four COD permits are available on a first-come, first-served basis to all four domains (0, 1, 2, and 3). Notes on Domain Configuration Note the following points when you configure domains using resources on COD boards. ■ To set the COD board to Uni-XSB When 3 COD permits or less are allocated to a COD board, there are CPUs which can't be used in Uni-XSB.
Note – Once you have used headroom to activate a COD resource, you are contractually obligated to purchase a COD permits for it. By default, COD resources arrive with headroom disabled. You can use the setcod command to establish it. However, if you already have COD permits for all your COD resources, configuring headroom has no effect. In that case, you need to install additional COD boards to retain your headroom capacity. You can also reduce or disable headroom at any time.
Note – This manual is written based on the XCP 1093 firmware or later. When using the XCP 1092 or earlier, see the following table and confirm the corresponding commands.
Activating COD Resources ▼ To Purchase COD Hardware Activation Options When you use the unused COD CPU which is mounted on the COD board you've purchased, contact our sales representative to purchase the COD permits in accordance with the number of CPUs which you make available.
3. Verify that the key was added to the COD database: XSCF> addcodactivation -r The key you add should be listed in the output. See “To Display COD Permit Status” on page 13. 4. Save the key in a safe place where you can refer to it if the XCP configuration is reset, the COD database is lost, or some other event requires you to reinstall it. Note – Do not attempt to install the same COD key more than once, except as noted in Step 4. Doing so would be a contract violation.
▼ To Reserve COD Permits for a Domain You need to reserve COD permits only if you want to make sure a specific number of COD permits are allocated to a particular domain. 1. Log in to the XSCF console with platadm privileges. 2. Execute the setcod command with or without options. a. Execute the command with options: XSCF> setcod -d domain_id cod_cpu_quantity For example: XSCF> setcod -d 1 4 b. Execute the setcod command with no options.
▼ To Enable, Increase, or Decrease Headroom 1. Log in to the XSCF console with platadm privileges. 2. Execute the showcod command with no options. For example: XSCF> showcod Chassis HostID: 80e3e446 PROC Permits installed: 10 PROC Headroom Quantity: 0 PROC Permits reserved for domain PROC Permits reserved for domain PROC Permits reserved for domain PROC Permits reserved for domain 0: 1: 2: 3: 4 0 0 0 3. Type the setcod command, specifying headroom.
Headroom warning messages are similar to: codd[627]: COD PROC WARNING: Headroom Active: key(s) must be installed ▼ To Disable Headroom 1. Log in to the XSCF console with platadm privileges. 2. Execute the setcod command specifying headroom as zero: XSCF> setcod 0 3. Verify that the headroom is disabled by executing the showcod command. For example: XSCF> showcod Chassis HostID: 80d88800 PROC Permits installed: 8 PROC Headroom Quantity: 0 ... ▼ To Display COD Information 1.
2. Execute the showcod command. The output displays the server’s Chassis HostID, number of COD permits, headroom quantity, and number of COD permits reserved for each domain.
2. Execute the showcodactivation command. The output displays the resource description, COD permit version number, expiration date, number of COD permits, and COD permit status. For example: XSCF> showcodactivation Description ----------PROC Ver --01 Expiration ---------NONE Count ----8 Status -----GOOD To display COD permit information in raw key format (the complete COD key assigned by Fujitsu), use the -r option.
▼ To Display Usage Statistics for COD Resources 1. Log in to the XSCF console with platadm or platop privileges, or domainadm, domainop, or domainmgr privileges for a specific domain. 2. Execute the showcodusage command. The output displays a summary of COD permit usage by resource type and for each domain.
16 SPARC Enterprise Mx000 Servers Capacity on Demand (COD) User’s Guide • January 2012
Index A activating COD Resources, 8 C Capacity on Demand (COD), 1 boards, 1 COD Hardware Activation Option, 2 headroom, 5, 11, 12, 13 violation, 6 COD activation log, 3 COD hardware activation permits, 2 type, 3 commands, 6 addcodactivation, 6, 7, 8 addcodlicense, 7 deletecodactivation, 6, 7 deletecodlicense, 7 setcod, 4, 6, 7, 10, 11, 12 showcod, 7, 8, 10, 11, 12, 13 showcodactivation, 7, 9, 13, 14 showcodactivationhistory, 3, 7, 13 showcodlicense, 7 showcodusage, 7, 15 D domain domain configuration, 5
18 SPARC Enterprise Mx000 Servers Capacity on Demand (COD) User’s Guide • January 2012
