HP Instant Capacity User's Guide for Version 9.
© Copyright 2000-2008 Hewlett-Packard Development Company, L.P Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Guide.............................................................................................................11 Intended Audience................................................................................................................................11 New and Changed Information in This Edition...................................................................................11 Publishing History.......................................................................
2.6 Instant Capacity Compliance and Enforcement.............................................................................36 2.7 Configuration Change Notification.................................................................................................37 2.8 Core Activation................................................................................................................................38 2.8.1 Increasing Processing Capacity by Purchasing RTUs...........................................
.2.1 HP-UX Licensing and Support with Temporary Instant Capacity.........................................76 5.2.2 OpenVMS Licensing and Support with Temporary Instant Capacity....................................76 5.3 Using Temporary Instant Capacity.................................................................................................77 5.3.1 Acquiring and Configuring Temporary Instant Capacity......................................................77 5.3.2 Using Temporary Instant Capacity........
7.14.5 Other Considerations...........................................................................................................122 7.14.6 Additional HA Solutions.....................................................................................................122 7.14.7 Summary of Rights Seizure.................................................................................................122 7.15 Considerations for Multiple Groups...................................................................
A.13.1 Customer protections which iCAP assumes to be in place................................................200 A.13.2 Disabling the iCAP daemon (HP-UX)................................................................................200 A.13.3 Customer Security Requirements.......................................................................................200 A.13.4 Security Tuning Options.....................................................................................................
List of Figures 1-1 4-1 4-2 4-3 4-4 4-5 4-6 4-7 4-8 4-9 4-10 5-1 6-1 6-2 6-3 7-1 8 Instant Capacity System Elements................................................................................................21 Permanent Activation of Instant Capacity Components..............................................................54 Partition premodification state: One cell assigned with 3 active and 1 inactive cores, and usage rights for 2 additional cores......................................................
List of Tables 1-1 6-1 6-2 9-1 9-2 A-1 B-1 B-2 Most Recent Instant Capacity Versions and Supported Platforms...............................................23 Cell Board Activation Not Requiring Additional Core Usage Rights..........................................94 Cell Board Activation Requiring Additional Core Usage Rights.................................................94 Email sent by the Instant Capacity software...............................................................................
List of Examples 2-1 4-1 4-2 4-3 4-4 4-5 4-6 4-7 5-1 5-2 5-3 5-4 5-5 5-6 5-7 7-1 7-2 7-3 7-4 8-1 A-1 10 Configuration Change Notification email for Instant Capacity System (not vPar)......................37 Sample Session of icapstatus (on HP-UX).....................................................................................51 Applying an RTU Codeword (HP-UX).........................................................................................53 Activating an Additional Core (HP-UX)...............
About This Guide The HP Instant Capacity User’s Guide for Version 9.x provides you with the most recent information for using the Instant Capacity version 9 software. This document describes Instant Capacity version B.11.31.09.00.00 on HP-UX 11i v3 systems, B.11.23.09.00.00 on HP-UX 11i v2 systems, B.11.11.09.00.00 on HP-UX 11i v1 systems, and Instant Capacity version 8.1 on OpenVMS 8.3-1H1 Integrity servers. The latest version of this document can be found online at: http://docs.hp.com.
Publishing History The document printing date and part number indicate the document’s current edition. The printing date will change when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number will change when extensive changes are made. Document updates may be issued between editions to correct errors or document product changes.
Document Organization This user’s guide is not designed to be read from front to back in its entirety. To get an understanding of Instant Capacity version 9.x, you should read this chapter, Chapter 1 - Instant Capacity Overview, and Chapter 2 - Getting Started. After reading these chapters, you can utilize the table of contents and index (in back) for specific topics of interest. • • • • • • • • • • • • • • About This Guide provides an introduction to this guide and locating Instant Capacity information.
Typographic Conventions This document uses the following conventions: %, $, or # audit(5) Command Computer output Ctrl+x ENVIRONMENT VARIABLE [ERROR NAME] Key Glossary term User input Variable [] {} ... | WARNING CAUTION IMPORTANT NOTE 14 A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne, Korn, and POSIX shells. A number sign represents the superuser prompt. A manpage. The manpage name is audit, and it is located in Section 5.
Location of Instant Capacity Information Instant Capacity User’s Guide for Version 9.x You can find the HP Instant Capacity User’s Guide for Version 9.x in the following locations: • On the HP Documentation website: http://docs.hp.com These are the most current release notes and the most current localized versions.
Manpages NOTE: The information contained in this section applies only to HP-UX systems. It does not apply to Integrity servers running OpenVMS.
1 Introduction to Instant Capacity This chapter covers the following topics: • “Instant Capacity Summary” (page 18) • “Overview” (page 20) For more in-depth information, see icap(5).
1.1 Instant Capacity Summary HP Instant Capacity software provides the ability to instantly increase or decrease computing capacity on specified HP enterprise servers. NOTE: HP Instant Capacity for HP 9000 and HP Integrity Servers, also known as Instant Capacity or iCAP, was known in earlier versions as Instant Capacity on Demand, or iCOD. Although the commands, warning messages and error messages refer to the software as iCAP, some internal files might still refer to iCOD.
This document provides you with the most recent information about using the Instant Capacity version 9.x software to manage processing capacity in your HP enterprise server. NOTE: All personnel with system administrator access (that is, root login privileges) to an Instant Capacity system should read and understand the contents of this document and the implications of increasing or decreasing processing capacity. 1.1.
1.2 Overview 1.2.1 Software Product Overview The following Instant Capacity software products are associated with HP’s Utility Pricing Solutions program: • iCOD: HP product number B9073BA (HP-UX) • iCAP: HP OpenVMS product number BA484AA This user's guide contains information for Instant Capacity version 9.x on HP-UX systems and version 8.1 on OpenVMS systems. Instant Capacity must be run on a partitionable system.
Figure 1-1 Instant Capacity System Elements System Compliance iCAP DB Codeword Generation Record Purchase iCAP Admin System iCAP Web Portal HP Sales Rep. Request Codeword Asset Report Purchase Customer Notification Status and Control iCAP Software Other System Management Commands Authorization Status and Control Status and Control Cores, Cells and Memory 1.2.2.
• • Monitor and report system compliance (icapd daemon on HP-UX, ICAP_SERVER process on OpenVMS). Manage Global Instant Capacity groups (icapmanage command). For details about these commands on HP-UX, see “Instant Capacity HP-UX Manpages” (page 141). For the OpenVMS equivalents of these commands, see “DCL Commands” (page 204). 1.2.2.3 Utility Pricing Solutions Portal The Utility Pricing Solutions (or Instant Capacity) portal is located at the HP web site: http://www.hp.
1.2.3 Most Recent Instant Capacity Product Versions and Supported Platforms Table 1-1 lists the current versions of Instant Capacity and the platforms supported for each version. Table 1-1 Most Recent Instant Capacity Versions and Supported Platforms Software and Version iCOD Operating System Version HP-UX 11i v3 B.11.31.09.00.00 (B9073BA) Supported Hardware Platforms HP Integrity servers: • Superdome • rx8640 • rx8620 • rx7640 • rx7620 Notes Available on: • http://www.hp.
1.2.4 Past Versions and Supported Operating Systems Previous versions of the Instant Capacity software are as follows: • B.01.00 (on HP-UX 11.00) • B.02.x (on HP-UX 11.00 and 11i v1) • B.03.x (on HP-UX 11i v1) • B.04.x (on HP-UX 11.00 and 11i v1) • B.05.00 (on HP-UX 11.00 and 11i v1) • B.06.x (on HP-UX 11i v1 and 11i v2) • B.07.x (on HP-UX 11i v1 and 11i v2) • B.08.00 (on HP-UX 11i v1 and 11i v2) • B.08.00.01 (on HP-UX 11i v1 and 11i v2) • B.08.01.01 (on HP-UX 11i v1, 11i v2 and 11i v3) • B.08.
2 Getting Started This chapter covers the following topics: • “Instant Capacity Requirements” (page 26) • “Instant Capacity Components” (page 31) • “Global Instant Capacity” (page 33) • “Instant Capacity Codewords” (page 34) • “Temporary Instant Capacity” (page 35) • “Instant Capacity Compliance and Enforcement” (page 36) • “Configuration Change Notification” (page 37) • “Core Activation” (page 38) • “Instant Capacity Cell Board” (page 39) • “Instant Capacity Software Validation” (page 40) • “Status Reporti
2.1 Instant Capacity Requirements 2.1.1 Program Requirements To participate in the Instant Capacity version 9.x program, you must comply with the following conditions of the HP Utility Pricing Solutions program: • • Maintain the HP Instant Capacity software on each HP-UX or OpenVMS partition in the system. The Instant Capacity software is a nonintrusive, low-overhead software module that resides on the partition. Migrate to later Instant Capacity software versions as they become available.
the managers and members of groups is established using SSL certificates that are supplied by the GiCAP software. 2.1.2.2 Required Patches for HP-UX 11i v1 The following patches are required for Instant Capacity version 9.x on HP-UX 11i v1: • • • • • • • • • PHKL_22987: S700_800 MeasureWare software) PHKL_23154: S700_800 PHKL_25218: S700_800 fix PHKL_26232: S700_800 PHKL_30197: S700_800 PHCO_24396: S700_800 PHCO_24477: S700_800 PHCO_29832: S700_800 PHCO_29833: S700_800 11.
IMPORTANT: For the most recent required patches, see the Instant Capacity Installation page on the HP Software Depot (search for “B9073BA”): http://www.hp.com/go/softwaredepot 2.1.2.5 HP-UX 11i v3 Requirements and Dependent Products The following software is required for Instant Capacity version 9.x on HP-UX 11i v3: • • • • • • • HP-UX 11i v3 iCOD software bundle B9073BA (version 9.
NOTE: Starting with iCAP version 8.02, asset reporting is turned off by default for new installations. However, for reinstallation and upgrades the asset reporting remains at its previous setting; if your system was manufactured prior to iCAP version 8.02, asset reporting might still be turned on. Unless you turn off asset reporting or configure the email connectivity, error messages are logged when the software attempts to send asset reports.
The Instant Capacity software must be installed on all virtual partitions in an Instant Capacity system. For details about virtual partitions, see the Installing and Managing HP-UX Virtual Partitions manual on the HP Documentation website: http://docs.hp.
2.2 Instant Capacity Components 2.2.1 Overview The Instant Capacity software monitors and enforces compliance with contractual agreements. It authorizes or denies activation of system components (cores, cells, memory) based on a complexwide database of usage rights. For details about acquiring additional usage rights, see “Usage Rights Requirement” (page 29). Activation of components is restricted according to complexwide compliance for each component type.
components can be conveyed with a single RTU codeword, it is particularly useful to anticipate the core and memory needs when purchasing cell-board usage rights. As with other components, the Instant Capacity software enforces compliance for memory by comparing the actual amount of inactive memory with the expected inactive memory. IMPORTANT: 32 Getting Started You must have one active core for each active cell board.
2.3 Global Instant Capacity Global Instant Capacity, or GiCAP, provides HP customers with the flexibility to move usage rights for Instant Capacity components within a group of servers. It also provides “pooled” temporary capacity across the group. This provides more cost-effective high availability, including disaster recovery capabilities, more adaptable load balancing, and more efficient and easier use of temporary capacity.
2.4 Instant Capacity Codewords Instant Capacity uses codewords for several purposes: to adjust available usage rights for system components (RTU codewords), to apply temporary capacity to the system, and to apply sharing rights to a GiCAP Group Manager system to enable the creation of one or more groups. All types of codewords must be purchased as specific product numbers from HP. After purchase, the actual codeword (an encrypted string) can be retrieved from the Utility Pricing Solutions web portal.
2.5 Temporary Instant Capacity You can purchase an amount of temporary processing capacity for your Instant Capacity system. Temporary Instant Capacity, or TiCAP, is purchased in units of processing days. TiCAP allows one or more cores beyond the count allowed by the available usage rights to be activated for up to the specified period of prepaid minutes without requiring the purchase of additional usage rights.
2.6 Instant Capacity Compliance and Enforcement The Instant Capacity software primarily maintains complexwide information about the usage rights and activation of system components. The software monitors the number of usage rights for the entire complex for each type of component. (If you are using Global Instant Capacity, the software also maintains groupwide information about usage rights. For more information about GiCAP, see Chapter 7.
2.7 Configuration Change Notification Specifying an increase or decrease in the number of active cores (using the icapmodify command) causes a core configuration change. An email notification is sent to the system contact when a change occurs that affects the configuration of cores.
2.8 Core Activation As previously described, an Instant Capacity system contains a specified quantity of activated processing capacity (cells, cores, and memory) and a specified amount of deactivated processing capacity. Systems can have fewer active components than they have rights to activate. Such systems can instantly activate additional components without the need to purchase an RTU, up to the number of component usage rights on the system. 2.8.
2.9 Instant Capacity Cell Board Instant Capacity Cell Board allows you to have additional (inactive) cell-board capacity in your system for growing business needs. When the need arises, you can purchase additional cell and memory usage rights; then the inactive cell boards, which contain memory and cores, are available for instant activation and use. The Instant Capacity software monitors and enforces the count of inactive cell boards (those without usage rights) throughout the complex.
2.10 Instant Capacity Software Validation 2.10.1 On HP-UX Systems The Instant Capacity software (HP-UX product B9073BA) is installed by HP manufacturing on instantly ignited HP-UX systems. The Instant Capacity software can also be installed by an HP service representative on existing (supported) HP-UX enterprise servers as an add-on. NOTE: The Instant Capacity software is automatically installed when the HP-UX 11i v3, 11i v2, or 11i v1 Operating Environment (OE) is installed.
2.11 Status Reporting on Instant Capacity Systems You can use the icapstatus command to view the status of your Instant Capacity system.
2.12 Time Zone Considerations On HP-UX systems, the icapd daemon performs routine Instant Capacity software tasks on a daily basis. A partition’s local time zone setting affects what time zone the icapd daemon uses for the timing of these tasks Be sure that the time zone is set properly to ensure synchronization among the partitions. Because the HP-UX icapd daemon is started by init, the /etc/default/tz file must contain the desired time zone specification. By default, the time zone is set to EST5EDT.
3 Installing and Removing Instant Capacity Software This chapter covers the following topics: • “Installing Instant Capacity Software” (page 44) • “Reinstalling Instant Capacity Software” (page 46) • “Removing Instant Capacity Software” (page 47) 43
3.1 Installing Instant Capacity Software Factory Integrated Systems The Instant Capacity software is installed by HP on all HP enterprise servers, even those without Instant Capacity components. To verify that the software is installed and configured, use the following HP-UX command : /usr/sbin/swverify iCOD The command output displays the message Verification succeeded .
swinstall -s /dvd B9073BA 6. Continue with “For All HP-UX Installations” (page 45). 3.1.2 Installing from the HP Software Depot (For HP-UX 11i v1, 11i v2, and 11i v3): 1. 2. 3. Search for B9073BA on the HP Software Depot website: http://www.hp.com/go/ softwaredepot Select the link that appeared as a result of your search, and follow the instructions on the Installation page. Continue with “For All HP-UX Installations” (page 45). 3.1.
3.2 Reinstalling Instant Capacity Software 3.2.1 Preserving current Instant Capacity information If you reinstall HP-UX on a partition with Instant Capacity (for example, installing HP-UX by either cold-installing or installing from a golden image), you must perform the following steps. Otherwise, all information in the Instant Capacity configuration file (change history, system contact information) is lost.
3.3 Removing Instant Capacity Software IMPORTANT: Do not attempt to remove the Instant Capacity software. 3.
4 Using Instant Capacity to Manage Processing Capacity This chapter covers the following topics: • “Checking the Status of your Instant Capacity System” (page 50) • “Setting System Contact Information” (page 52) • “Applying a Right To Use (RTU) Codeword” (page 53) • “Activating Cores” (page 55) • “Deactivating Cores” (page 57) • “Overriding Deferred Activation and Deactivation” (page 59) • “Load-Balancing Active Cores” (page 60) • “Understanding and Managing Intended Active Values” (page 61) • “Activations
4.1 Checking the Status of your Instant Capacity System You can use the icapstatus command to view the status of your Instant Capacity system.
— — — — Inactive memory Inactive cells Runs iCAP (indicates whether the hard partition contains compatible Instant Capacity software) nPar name For details about the icapstatus command and its output, see icapstatus(1M). Example 4-1 Sample Session of icapstatus (on HP-UX) > /usr/sbin/icapstatus Software version: System ID: Serial number: Product number: Unique ID: System contact e-mail: From e-mail: Asset reporting: Temporary capacity warning Exception status: B.11.31.09.00.00.
4.2 Setting System Contact Information HP recommends that you specify a system contact’s email address on each partition in your system. On OpenVMS systems, the email address may be a logical pointing to a distribution list.
4.3 Applying a Right To Use (RTU) Codeword Unless you have a balance of Instant Access Capacity (IAC) or temporary capacity (or usage rights available from a GiCAP group), you must purchase additional usage rights before activation of an inactive core. To purchase additional usage rights: 1. 2. 3. Contact your HP sales representative to purchase the appropriate Instant Capacity RTU products. Acquire an RTU codeword from the Utility Pricing Solutions web portal at http:// www.hp.com/go/icap/portal.
Figure 4-1 Permanent Activation of Instant Capacity Components Customer Order iCAP System/ Components Apply IAC Codeword to System Additional Core Capacity Needed Consumption of IAC Halted Acquire IAC Codeword from Portal Activate Component(s) Using IAC Apply RTU Codeword to System Order iCAP RTU(s) Acquire RTU Codeword from Portal HP (or rep) Installs iCAP System/ Components HP Ship iCAP System/ Components 54 Send Ack Letter Post IAC in iCAP DB Using Instant Capacity to Manage Processing Capa
4.4 Activating Cores The icapmodify command provides the ability to increase processing capacity instantly by activating cores with available usage rights in Instant Capacity systems. At any time, any number of inactive cores with usage rights can be activated, as long as sufficient usage rights are available. Whether you are activating or deactivating cores, the icapmodify command adjusts only the number of dynamic cores, and it does not explicitly identify specific cores.
and the virtual partition allows enough additional cores to fulfill the request . Otherwise, use the parmodify command to reconfigure the nPartitions, or use the vparmodify command to remove cores from other virtual partitions within the same nPartition (essentially adding to the unassigned pool). 4.4.1 Example Core Activation Session Example 4-3 shows how to activate an additional core in an nPartition environment.
4.5 Deactivating Cores You can decrease processing capacity instantly on HP enterprise servers with the Instant Capacity software (even on servers with sufficient usage rights for all cores to be active simultaneously). Any number of active cores can be deactivated at any time, within the following partition constraints. Core deactivation can be useful for load balancing cores in nPartitions (hard partitions) of Instant Capacity systems.
Example 4-4 Deactivating an Active Core (HP-UX) > /usr/sbin/icapmodify -d 1 2 cores are intended to be active and are currently active. NOTE: In Example 4-4, the core deactivation is instant (that is, does not require a reboot). To defer deactivation until the next reboot, use the -D option with the command. For details, see icapmodify(1M). The icapmodify command allows you to either deactivate cores with the -d option or to set the total number of active cores with the -s option.
4.6 Overriding Deferred Activation and Deactivation NOTE: Although this section discusses only activation of cores, the discussion applies also to deactivation of cores. If you have performed a deferred core activation (using the icapmodify -D command), and the intended number of active cores specified is no longer desirable, you can override the (pending) deferred activation by performing another deferred or instant icapmodify operation. This second operation overrides the first activation.
4.7 Load-Balancing Active Cores Active cores can be redistributed across any or all partitions of a hardware-partitionable system if those partitions contain inactive cores. For example, consider a system with two partitions: • • Partition 1 has 5 active cores and 3 inactive cores. Partition 2 has 8 active cores and 0 inactive cores. You need to add processing power to Partition 1 because of application demand and you notice that the active cores in Partition 2 are underutilized.
4.8 Understanding and Managing Intended Active Values The Instant Capacity software maintains a value for each nPartition of a complex called intended active. Fundamentally, the intended active value is the number of cores intended to be active after a reboot of the nPartition. The concept and proper manipulation of intended active is critical because: • • It determines the number of cores which will be active upon the boot of an nPartition.
4.9 Activations and Deactivations in a Virtual Partition Environment Instant Capacity can be present on HP-UX systems or partitions where virtual partition technology is employed. In a virtual partition environment, cores that are not assigned to any virtual partition are considered inactive (in addition to other classes of inactive cores).
NOTE: The icapstatus command output indicates that the number of cores that can be assigned (to the local virtual partition) is zero if the static resource attribute for the local virtual partition is set. 4.9.4 Activating Cores in a Virtual Partition Environment In a virtual partition environment, the icapmodify command must be used to modify processing capacity when you are making any adjustment to an nPartition or to multiple nPartitions.
4.9.6 Boot Time Compliance A compliance check is performed whenever a virtual partition is booted. If the total number of cores assigned to all virtual partitions in the current vPar database exceeds the nPartition’s intended active core count, the Instant Capacity software notifies the vPar monitor.
4.10 Assigning a Cell to a Partition A cell can be assigned to a partition only if sufficient cell usage rights are available across the complex, as well as sufficient memory usage rights to enable activation of all the memory on the cell, and sufficient usage rights for at least one core of the cell to be active.
NOTE: Cell boards are assigned to specific partitions and cannot be shared between partitions. All cores on a cell board are accessible by only the partition to which the cell board is assigned. Cores on one cell board cannot be shared across multiple partitions.
4.11 Unassigning a Cell from a Partition When a cell is unassigned from a partition in an Instant Capacity system, the number of intended active cores in the partition decreases only if the number of cores being removed with the cell is greater than the number of expected inactive cores in the partition.
Figure 4-9 Partition postmodification state: Unassigned Cell 3 (total of 8 active cores are set) Cell 1 A A A Cell 2 A A A A A Figure 4-10 Postmodification state: Unassigned Cell 3 with 4 inactive cores, with usage rights available for 1 additional core Available Usage Rights Cell 3 I I I I UR When Cell 3 is unassigned from the partition, the number of intended active cores changes from 9 to 8 (because 8 is the total number of cores remaining in the partition).
4.12 Software Application Considerations Some software applications size themselves based on the number of available cores when the application is started. If an application is running when an additional core is activated, the application might not recognize the newly activated core as available for processing.
4.13 Test Activation of Cores Using Temporary Capacity You might want to test your software application for proper operation and improved performance by activating an additional core. The use of temporary capacity or Instant Access Capacity (IAC) is required for activation of a core without usage rights for testing purposes. For details, see Chapter 5: “Temporary Instant Capacity” (page 73). The following testing guidelines are meant to be an aid to your test plan.
4.14 Replacement of Failed Cores 4.14.1 HP-UX LPMC and HPMC If an active core fails with a Low Priority Machine Check (LPMC) in a partition with Instant Capacity, its processing capacity is replaced instantly by an inactive core, if any are available in the partition. The failed core is marked for deconfiguration during the next system reboot. For additional considerations in a virtual partition environment, see “LPMC Deactivations in Virtual Partitions” (page 71).
If there are multiple active processors in your system, one of them is designated as the primary processor and the other (nonprimary) processors can be replaced on line. If the primary processor fails, it cannot be replaced without a reboot.
5 Temporary Instant Capacity This chapter covers the following topics: • “Temporary Instant Capacity Overview” (page 74) • “Ordering Temporary Instant Capacity” (page 76) • “Using Temporary Instant Capacity” (page 77) • “Temporary Capacity and Virtual Partitions” (page 79) • “Tracking Usage of Temporary Instant Capacity” (page 81) • “Temporary Instant Capacity Warning Period” (page 83) • “Temporary Instant Capacity Expiration and Compliance Enforcement” (page 84) • “Temporary Instant Capacity Exceptions” (p
5.1 Temporary Instant Capacity Overview You can purchase an amount of temporary capacity (TiCAP) time for inactive cores without usage rights in your Instant Capacity system. Temporary capacity can be purchased in units of processing days. Temporary capacity allows one or more inactive cores to be activated for up to the specified period of prepaid processing time, without requiring permanent usage rights for the cores.
Figure 5-1 Using Temporary Instant Capacity: Temporary Activation of Cores Without Usage Rights Customer Order iCAP System/ Components HP (or rep) Installs iCAP System/ Components Prior to Needing Additional Core Capacity Order TiCAP Additional Core Capacity Needed Apply TiCAP Codeword to System Activate Core(s), with -t option Acquire TiCAP Codeword from Portal Deactivate Core(s) HP Ship iCAP System/ Components Send Ack Letter Process Order for TiCAP Post TiCAP Order in iCAP DB 5.
5.2 Ordering Temporary Instant Capacity To add temporary capacity credits to a system, order the desired quantity of the Temporary Instant Capacity product for your type of server. The system serial number is required for orders of Temporary Instant Capacity. Instant Capacity cores that are added to an existing system can include some additional temporary capacity called Instant Access Capacity (IAC).
5.3 Using Temporary Instant Capacity 5.3.1 Acquiring and Configuring Temporary Instant Capacity To add temporary capacity to a system that contains Instant Capacity cores (cores without usage rights), follow this procedure: 1. Order the desired amount of Temporary Instant Capacity for your type of server by submitting a purchase order to HP. Be sure to specify the system serial number.
Example 5-2 Activating an Instant Capacity Core with Temporary Capacity (HP-UX) > /usr/sbin/icapmodify -t -a 1 3 cores are intended to be active and are currently active. Number of cores using temporary capacity: 1 Projected temporary capacity exporation: 12/22/08 08:00:00 NOTE: Temporary capacity cannot be used to activate Instant Capacity cores in inactive Instant Capacity cell boards. You must purchase additional usage rights for the cell board and perhaps also for the memory of the cell board.
5.4 Temporary Capacity and Virtual Partitions If temporary capacity is being consumed in any virtual partition environment (previously authorized with icapmodify -a n -t), deactivating a core with the vparmodify -d command temporarily reduces the consumption of temporary capacity, although there may be a delay of up to 30 minutes for the consumption of temporary capacity to cease.
8 9 10 11 12 13 N/A 80 0 0 0 0 0 0 8 1 4 4 4 4 4 N/A Temporary Instant Capacity 4 4 4 4 4 4 N/A 3 0 0 0 0 0 8 0.0 0.0 0.0 0.0 0.0 0.0 4.
5.
Example 5-4 Temporary Capacity Expiration Reminder To: root@par1.yourorg.com Subject: Temporary Capacity Expiration Reminder *************************************************************************** **** Failure to perform the following steps will result in the complex **** **** attempting to deactivate cores on any booting partitions until **** **** the complex is in compliance with the Instant Capacity contract.
5.6 Temporary Instant Capacity Warning Period By default, the Instant Capacity software sends the expiration reminder when the temporary capacity balance is projected to expire within 15 days. You can adjust that warning period by specifying a different value with the icapmodify command, using the -w option. For example, the following command specifies a longer warning period, for more advance notice: > icapmodify -w 20 The Temporary Capacity Warning Period has been successfully set to 20 days. 5.
5.7 Temporary Instant Capacity Expiration and Compliance Enforcement IMPORTANT: If you leave cores without usage rights activated beyond the purchased temporary capacity duration, the software automatically deactivates one or more cores on the next reboot of any partition in the complex. If you leave cores without usage rights activated on OpenVMS systems, the ICAP_SERVER process automatically deactivates one or more cores within one half hour on any partition in the complex.
5.8 Temporary Instant Capacity Exceptions 5.8.1 Error for Activation with Insufficient Temporary Capacity You cannot activate an Instant Capacity core with temporary capacity unless there is a sufficient balance of temporary capacity available. For details on how to increase the temporary capacity balance, see “Acquiring and Configuring Temporary Instant Capacity” (page 77).
Example 5-6 Error Message for Temporary Capacity Partial Enforcement To: root@par1.yourorg.com Subject: Instant Capacity enforcement notice This message is being sent to inform you that, due to expiration of temporary capacity, 1 additional core(s) were deactivated on your Instant Capacity system (containing the partition par1) to bring the complex into compliance. Prior to deactivation, the number of active cores exceeded the number of available core usage rights by 3.
Example 5-7 Error Message for Temporary Capacity Complete Enforcement To: root@par1.yourorg.com Subject: Instant Capacity enforcement notice This message is being sent to inform you that, due to expiration of temporary capacity, 1 core(s) were deactivated on your Instant Capacity complex (containing the partition par1) to bring the complex into compliance with the Instant Capacity contract. Prior to deactivation, the number of active cores exceeded the number of available usage rights by 1.
6 Instant Capacity Cell Board This chapter covers the following topics: • “Instant Capacity Cell Board” (page 90) • “Ordering Instant Capacity Cell Board” (page 91) • “HP-UX and OpenVMS License and Support” (page 92) • “Acquiring Usage Rights for Instant Capacity Cell Board” (page 93) • “Instant Capacity Cell Board and Considerations of Core Usage Rights” (page 94) • “Activation of an Instant Capacity Cell Board” (page 95) • “Accidental Activation of an Instant Capacity Cell Board” (page 96) • “Instant Capa
6.1 Instant Capacity Cell Board 6.1.1 Overview Instant Capacity Cell Board offers a way to have additional (inactive) cell board capacity in your system for growing business needs. When the need arises, you acquire the necessary usage rights in order to activate and use the cell boards, which contain memory and processors or cores.
6.2 Ordering Instant Capacity Cell Board To order the Instant Capacity Cell Board product, do the following: • • • Order the appropriate HP product number for the cell board for your specific class of HP server. Order the appropriate HP product number for the entire amount of Instant Capacity memory on the cell board.
6.3 HP-UX and OpenVMS License and Support You do not initially pay for HP-UX and OpenVMS license and support fees on an Instant Capacity cell board. When you acquire the usage rights for a cell board by purchasing the cell board RTU product, there is an additional cost for the incremental HP-UX or OpenVMS license and support for each core that is activated. That is, the HP-UX or OpenVMS license and support costs are based on a “per active core” basis and are not included as part of the cell board RTU.
6.4 Acquiring Usage Rights for Instant Capacity Cell Board Before activation of an (inactive) Instant Capacity cell board, you must acquire (purchase, or borrow from a GiCAP group) additional usage rights from HP. To purchase additional usage rights: • • • Order the appropriate HP RTU product for the cell board for your specific class of HP server. Order the appropriate HP RTU product for the entire amount of Instant Capacity memory on the cell board.
6.5 Instant Capacity Cell Board and Considerations of Core Usage Rights At least one core usage right must be available for an Instant Capacity cell board you want to activate. Each active cell board must have at least 1 active core. However, you do not necessarily need to acquire additional core usage rights. No additional core usage rights are required unless the requirement for a minimum of 1 core per active cell board cannot otherwise be met.
6.6 Activation of an Instant Capacity Cell Board An Instant Capacity cell board is usually assigned to an nPartition; however, the cell board does not participate in the boot of the nPartition. Activating an Instant Capacity cell board is a two-step process: 1. 2. Set the cell board’s use-on-next-boot flag to y (yes) using the parmodify command. Reboot the nPartition (using the shutdown -r command on HP-UX), or (on HP-UX 11.31 OEUR 0709 or later) a Cell Online Activation.
6.7 Accidental Activation of an Instant Capacity Cell Board If you accidentally activate an Instant Capacity cell board, you can deactivate it by following this two-step procedure: 1. 2. Set the cell board’s use-on-next-boot flag to n (no) by using the parmodify command. Reboot the nPartition, or (on HP-UX 11.31 OEUR 0709 or later) a Cell Online Deactivation. This step is not necessary if there was no reboot after the activation.
6.8 Instant Capacity Cell Board Activation Exception Error When you attempt to activate an Instant Capacity cell board in an nPartition, depending on the number of core usage rights that are currently available in the complex, there is a chance the number of intended active cores for the nPartition is out of compliance and the activation fails. Figure 6-1, Figure 6-2, and Figure 6-3 illustrate this.
6.9 Instant Capacity Cell Board and Temporary Instant Capacity You can activate cores only on activated cell boards for which cell board usage rights have been acquired. This is true for both permanent activation of a core and temporary activation of a core using temporary capacity. To acquire usage rights for an Instant Capacity cell board, you must acquire usage rights for the cell board and the entire amount of memory it contains.
7 Global Instant Capacity This chapter covers the following topics: • “Global Instant Capacity Overview” (page 100) • “Global Instant Capacity Requirements” (page 102) • “Global Instant Capacity Group Managers” (page 103) • “Global Instant Capacity Grouping Rules” (page 105) • “Global Instant Capacity Sharing Rights” (page 106) • “Creating Global Instant Capacity Groups” (page 107) • “Global Instant Capacity Resource Sharing” (page 110) • “Global Instant Capacity and Temporary Capacity” (page 113) • “Removi
7.1 Global Instant Capacity Overview Global Instant Capacity, or GiCAP, provides you with the flexibility to move usage rights for Instant Capacity components within a group of servers. It also provides “pooled” temporary capacity across the group. This has several potential benefits: cost-effective high availability, more adaptable load balancing, and more efficient and easier use of temporary capacity. A GiCAP Group is managed using the icapmanage command.
Figure 7-1 Using Global Instant Capacity Customer Select Group Manager System Purchase GiCAP Sharing Rights Codeword Add Member Systems to Group Apply Grouping Rules on Group Manager Acquire Grouping Rules from Portal Create GiCAP Group Apply Codeword on Group Manager Additional Capacity Needed on System A Excess Capacity on System B Deactivate Components on System B Activate Components on System A HP Send Acknowledgement Letter Process Order for Codeword Post GiCAP Order in iCAP Database 7.
7.2 Global Instant Capacity Requirements To use Global Instant Capacity, the Group Manager and all partitions on all servers in the group must be running Instant Capacity version 9.0 or later. Every GiCAP group member must be hardware-compatible with other GiCAP group members as determined by the GiCAP grouping rules. WBEM version A.02.05 or higher must be installed on the Group Manager and on all member systems in order to use GiCAP.
7.3 Global Instant Capacity Group Managers For each group, an HP-UX system must be designated as an active GiCAP Group Manager. This system maintains information about the group, group resources, and grouping rules. Use the icapmanage commands on a Group Manager system only. The active Group Manager must be an HP-UX system running Instant Capacity software version 9.0 or later.
In some circumstances, the cron job set up by the icapmanage -a -S command may stop running, perhaps due to another operation on the Group Manager system. The cron entry can be restored by any of the following methods: • • • Manually edit the crontab file and re-enter the icapmanage -t instruction. This is the preferred method. Remove and re-add the standby Group Manager. Run icapmanage -Q on the active Group Manager. This is not recommended because it might have some unexpected side effects.
7.4 Global Instant Capacity Grouping Rules A GiCAP group consists of a list of server complexes that are allowed to share Instant Capacity usage rights (for cores, cell boards, and memory) and temporary capacity. Other than performance considerations, there are no particular constraints on the number of servers allowed in a group, but there are grouping rules defined by HP to specify the types of servers allowed to group together.
7.5 Global Instant Capacity Sharing Rights Although GiCAP is part of Instant Capacity and is installed at the same time as Instant Capacity, it is not enabled during installation. To share resources across groups, you must purchase GiCAP sharing rights, acquire the GiCAP codeword from the HP Utility Pricing Solutions portal (http:// www.hp.com/go/icap/portal), and apply the associated codeword to the Group Manager system.
7.6 Creating Global Instant Capacity Groups After the sharing rights codeword and the grouping rules have been applied to the Group Manager, a GiCAP group can be created by issuing the icapmanage command using the -a, -g, and -m options. Use the -a option to add members, the -g option to select the group name, and the -m option to specify a name for the new member along with a list of hosts running on the system.
“IT” to that group. When you first add new members to a group, you are prompted for the root password for each specified host. The password is used only to establish secure communication and is not saved or stored. Example 7-3 Adding a Member to a Group > icapmanage -i -U /tmp/GiCAP.rules > icapmanage -T node.corp.com -g one root@mypar.node.corp.com’s password: The server(s) are compatible with GiCAP group one > icapmanage -a -m IT:node.corp.com -g one Member IT added to group one.
Example 7-4 Example Output of icapstatus for a Group Member System > /usr/sbin/icapstatus Software version: System ID: Serial number: Product number: Unique ID: System contact e-mail: From e-mail: Asset reporting: Temporary capacity warning Exception status: B.11.31.09.00.00.71 node USR4020003 A6093A Z3e0ec8e078cd3c7b mjones@corp.com Set to the default ('adm') on period: 15 days No exception Member zoo6 in GiCAP group MyGroup ---------------------------------Active Group Manager: node1.corp.
7.7 Global Instant Capacity Resource Sharing Once a group is established, Instant Capacity resources (core, cell board, memory usage rights, and temporary capacity) can be shared among all the members of the group. Resource sharing can occur in several ways: • • • • During creation of the group, some members might have unused usage rights, so that by simply joining the group, additional usage rights are available for use by any member of the group.
member system needs to be activated, the usage rights made available by the deactivated component can be taken by the system using temporary capacity. In this case you might need to use the -t option to the icapmodify command to activate the component on the third member system by using temporary capacity.
Example: Cell/Memory Sharing In this scenario, member1 of the group mygroup has an inactive cell it wants to activate, but no usage rights are available on the system. However, member2 of the group has available usage rights.
7.8 Global Instant Capacity and Temporary Capacity Temporary capacity can be shared across servers for better efficiency and ease of use. Temporary capacity within a GiCAP group is always available to all members of a group without the need to purchase temporary capacity for each server. You can exercise some control over how “willing” each GiCAP member system is to share temporary capacity by setting its “temporary capacity warning period”.
7.8.3 Temporary Capacity Prefetch Because temporary capacity is pooled for the group, adjustments to the temporary capacity balance can be made even when it is not being consumed. For performance reasons, the Group Manager anticipates potential future use of temporary capacity and might prefetch an amount of temporary capacity from one or more member systems.
7.9 Removing a Global Instant Capacity Group Member Before removing a member from a GiCAP group, all the borrowed usage rights must be returned and all outstanding loans reclaimed. Do this by deactivating resources on the member about to be removed. Loaned usage rights are reclaimed by deactivating enough resources elsewhere in the group to cover the loan. The reclamation of loaned usage rights on the member about to be removed does not require the activation of resources on that member.
7.10 Reinstalling a Group Member If a group member is reignited, use the icapmanage command as follows to reestablish communication between the newly ignited group member and the Group Manager: icapmanage -a -m : -g See the HP Instant Capacity Release Notes for more details about reestablishing SSL certificates.
7.11 Group Manager Availability (No Standby Manager) If the active Group Manager becomes unavailable and a standby Group Manager is not defined or not used, management of the GiCAP group is unavailable until the Group Manager is restored or replaced. The GiCAP group members continue to operate as isolated Instant Capacity systems, using whatever usage rights and temporary capacity they had available when the Group Manager became unavailable.
7.12 Group Manager Failover Considerations If the active Group Manager system becomes unavailable and a standby Group Manager has previously been defined, the standby Group Manager can be used to take over GiCAP group operations from the Group Manager.
7.13 Upgrades and Global Instant Capacity Be careful before upgrading or changing hardware or operating systems for any member of a GiCAP group. If a member of a GiCAP group changes hardware in such a way that the hardware is no longer compatible with the group, then the group is considered to be out of compliance and group functions are restricted.
7.14 Rights Seizure GiCAP disaster recovery was introduced in Instant Capacity version 8.02.01 and provides the ability to “seize” core usage rights from a GiCAP member that is off line because of some disaster, and transfer them to the Group Manager. Then, using normal activation commands, these usage rights can be used to activate additional processor cores on other group members to increase capacity. Rights seizure can be used to provide disaster recovery when all partitions of a GiCAP member fail.
As a result, there are different behaviors and constraints depending on whether any partitions can be contacted on the specified member complex. If, at the time of rights seizure, at least one member partition can be contacted, then the software is able to make an immediate adjustment to the available core usage rights, just as if a normal migration operation using icapmodify -d had been performed before the specified hard partition stopped running.
seized usage rights in order to stop using temporary capacity. If this happens, the seized usage rights are no longer available for the failover activation. By specifying the use of temporary capacity on failover activation, you guarantee that the core activations needed for failover will occur. The total temporary capacity consumption across the group remains the same, even though the temporary capacity might be consumed on the failover server instead of on the original server.
flag to false for an inactive cell also releases the cell usage right and associated memory usage rights. • Maximum core usage rights are seized. There is no way to specify the number of core usage rights that are seized. Instant Capacity seizes the maximum number possible, while ensuring that the nPartition can still be booted. This seizure results in a partition with one core usage right for each active cell upon reboot of the server.
• • If there are multiple VM guests for the hard partition, they will be affected by the reduction of usage rights. In an HP Integrity VM environment, specify rights seizure only for the VM host, not the guests. The Group Manager must have network connectivity. If the Group Manager is also unavailable, and a standby Group Manager is not defined, it is not possible to transfer usage rights to a standby server.
7.15 Considerations for Multiple Groups You can create multiple GiCAP groups, and they can be managed by the same Group Manager or by different Group Manager systems. Note that if a Group Manager has an associated standby Group Manager, the standby Group Manager functions as a standby for all the groups managed by that Group Manager. A server complex can be a member of only one GiCAP group at a time.
7.16 Additional Considerations Systems that do not have any Instant Capacity components can be part of a GiCAP group. Deactivating resources on these systems allows them to loan usage rights to other members in the group. Members of a GiCAP group do not have to be located near each other. IP connectivity between the members, the Group Manager, and the standby Group Manager (if any), sufficient GiCAP sharing rights, and adherence to the GiCAP grouping rules are the only constraints.
8 Troubleshooting This chapter covers the following topics: • “Handling Compliance Exceptions” (page 128) • “Troubleshooting the Instant Capacity Software” (page 131) • “Diagnosing Email Configuration” (page 133) 127
8.1 Handling Compliance Exceptions A complex can get out of compliance with the Instant Capacity contract if any of the following occurs: • • • • • • More cells are active than expected (not enough inactive cells). More memory is active than expected (not enough inactive memory). More cores are active than expected (not enough inactive cores). There is a negative temporary capacity balance. (GiCAP) Sharing rights are insufficient. (GiCAP) Hardware is added that is incompatible with the group.
Example 8-1 Exception Report for More Cores Active than Expected To: root@par1.yourorg.com Subject: Instant Capacity Exception Report This message is being sent to inform you that your Instant Capacity complex (containing the partition par1) is in an exception state based on the following detected exceptions: More cores active than expected This complex is out of compliance with the Instant Capacity contract. The listed exceptions must be corrected as soon as possible.
turned off after a partition reboot, unassigned from partitions, or additional cell usage rights may be purchased for permanent activation. • More memory active than expected 'More memory active than expected' means that the amount of active memory across the complex exceeds the available memory usage rights. To find out how much inactive memory is expected on the complex, run icapstatus and look at the global amount of memory without usage rights.
8.2 Troubleshooting the Instant Capacity Software If the Instant Capacity software is not functioning, perform the following steps: 1. Verify that the Instant Capacity software is installed and not corrupted. On HP-UX systems, enter the following command: /usr/sbin/swverify iCOD You should see the message Verification succeeded. in the output of the swverify command.
On OpenVMS systems, verify the WBEM installation by using the following commands: $ cimprovider :== $WBEM_OPT:[wbem.bin]cimprovider $ pipe cimprovider -l | search sys$pipe “HP_NParProviderModule”,”HP_iCAPProviderModule”, ”HP_iCODProviderModule” HP_NParProviderModule HP_iCAPProviderModule HP_iCODProviderModule All three of the provider modules must be loaded. 8. 9. (HP-UX) Make sure partition commands, such as parstatus, are working.
8.3 Diagnosing Email Configuration Follow these steps to confirm the email configuration or to aid in debugging the configuration: 1. 2. 3. 4. Send an email message from your system to an email address in the same domain (intranet) and confirm receipt of the email message. Send an email message from your system to an email address outside of your domain (to the internet, for example, to a yahoo or hotmail email address) and confirm receipt of the email message.
9 Frequently Asked Questions This chapter covers frequently asked questions on the following topics: • “Instant Capacity Software” (page 136) • “Instant Capacity Hardware” (page 139) • “Global Instant Capacity” (page 140) 135
9.1 Instant Capacity Software What software product is required for Instant Capacity on Itanium-based servers running HP-UX? The HP software bundle for the Instant Capacity version 9.x software, on Itanium-based servers running HP-UX 11i v1, 11i v2, or 11i v3, is HP product number B9073BA. Can one HP enterprise server be under both a Pay per use (PPU) and Instant Capacity contract at the same time? No, the PPU and Instant Capacity software bundles are mutually exclusive.
How can I obtain codewords for newly purchased usage rights if the Utility Pricing Solutions portal is down? If the Utility Pricing Solutions portal is down, contact the HP Response Center. The Response Center can create an emergency codeword via the Instant Capacity codeword backup tool. What licensing is required for the Instant Capacity software? For Instant Capacity version 9.x, to activate additional components (cores, cell boards, or memory), you must acquire additional usage rights individually.
Table 9-1 Email sent by the Instant Capacity software (continued) Triggered By Email Message icapmodify (when a codeword is applied A warning message is sent to the system contact, if specified, and to a GiCAP member which modifies the root, stating that the Group Manager must adjust the number of number of cores without usage rights on that sharing rights.
9.2 Instant Capacity Hardware Can a faulty cell board be replaced with an inactive Instant Capacity cell board? Yes. First, deactivate the failed cell board by using the parmodify command and rebooting. Then activate the inactive iCAP cell board and reboot. In this situation, you do not need to obtain an RTU to activate the cell board. 9.
9.3 Global Instant Capacity Does HP know the configuration of the GiCAP groups? No. GiCAP group data is stored on the GiCAP Group Manager, which runs in the customer’s data center. The group configuration is limited by HP grouping rules, but information about groups or group members is not communicated to HP. Is GiCAP migration supported on a completely unavailable server? Yes. GiCAP Disaster Recovery is supported as long as the Group Manager is running Instant Capacity version 9.
Instant Capacity HP-UX Manpages 141
iCAP(5) NAME iCAP -- Instant Capacity software for HP-UX DESCRIPTION The HP Instant Capacity program provides services for instantly increasing or decreasing processing capacity on supported HP servers to meet varying system demands. An Instant Capacity server is an HP cellular (partitionable) server that is governed by an Instant Capacity contract constraining the number of cores, cell boards, and memory that must remain inactive at all times.
fee has been paid to HP for the type and number of components that are to be activated, RTU codewords are made available through the HP Utility Pricing Solutions portal (http:// www.hp.com/go/icap/portal). Instant Capacity codewords (such as RTU codewords) are applied to a complex using the icapmodify command on any partition of the complex. iCAP codewords are generated with a sequence number, and all iCAP codewords for a particular complex must be applied in the order in which they were generated.
Virtual Partitions Instant Capacity has a minimum version dependency on vPars A.03.05. For versions of vPars before A.03.05, the icapmodify command for activating or deactivating cores in a virtual partition fails with an error message indicating the vPars version dependency. Instant Capacity can be present on systems or partitions where virtual partition technology is employed.
capacity time. This allows temporary activation of cores without requiring the purchase and activation of an RTU codeword for permanent activation. Whenever an Instant Capacity component without usage rights is purchased, an amount of Instant Access Capacity (IAC) might also be included. Instant Access Capacity is exactly the same as temporary capacity, except it is automatically provided with an Instant Capacity component and is not separately purchased.
of servers allowed in a group, but grouping rules defined by HP specify the types of servers allowed to group together. GiCAP Group Manager For each group, an HP-UX system must be designated as an active Global Instant Capacity Group Manager. It is this system that maintains information about the group, group resources, and grouping rules. The icapmanage commands are intended to be used only on a Group Manager system to manage one or more GiCAP groups.
GiCAP codewords also have a sequence value and must be applied in the order in which they were generated for the Group Manager system. However, GiCAP codewords are sequenced independently from any other types of iCAP codewords that might be generated for the same system, and can therefore be applied independently from iCAP codewords.
Also, note that the number of available sharing rights is adjusted whenever an iCAP codeword is applied to a GiCAP member system which modifies the number of cores without usage rights on that member. (RTU and AddOn codewords for cores cause such adjustments.) If available sharing rights go negative (more in use than were purchased for the Group Manager), then all groups managed by that Group Manager are out of compliance and all group functions are restricted until the problem is resolved.
rights moves to the originally active Group Manager if it is requested to retake control, although only if the new active Group Manager is able to propagate its GiCAP database to the originally active Group Manager. For more details, see the “Group Manager Failover Considerations” section. Group Manager Failover Considerations If the active Group Manager system becomes unavailable, the standby Group Manager can take over GiCAP group operations from the Group Manager.
WBEM version A.02.05 or higher must be installed on the Group Manager and on all member systems in order to use Global Instant Capacity. The CIM Server configuration property sslClientVerificationMode must be set to a value of “optional” on all GiCAP Group Managers and on all OS instances of all member systems. (The CIM Server may need to be restarted if the property was not previously set to this value.) For details, see cimconfig(1M).
icapmanage(1M) NAME icapmanage -- Global Instant Capacity (GiCAP) management commands for GiCAP groups.
The icapmanage command can be used to install a grouping rules file, apply a GiCAP sharing rights codeword, create and remove GiCAP groups, test if a server can be added to a GiCAP group, update a GiCAP group by adding or removing members, show grouping rules and supported hardware, seize core usage rights from member partitions of a GiCAP group to be used by another member of the group, restore seized core usage rights to the original member partition, update an existing GiCAP member by adding or removing
Add a member (a partitionable complex) to a group, with -m :[,]... name member_name. Specify an OS instance (host) for each nPartition or virtual partition of the complex (do not specify virtual machine or guest OS instances). A member of a group must encompass all nPar and vPar OS instances of a complex, and each OS instance specified as a host must be accessible (ping-able) in order for the command to succeed.
When used in combination with the -S option, removes the identified host system from use as a standby Group Manager. -s -t -u Request status about one or more GiCAP groups. Specification without any additional options displays group and member information for all GiCAP groups managed by this Group Manager. Use the -g option to limit the information to the named group only. Use -b to display group-level information only.
-v Provide verbose status information. Include all levels of information (group, manager and member). For Group Managers, include resources being held by the Group Manager including temporary capacity. For members, include borrow and loan information as well as partition-specific information such as the allocation of resources among the hard partitions, and partition-specific information about seized or seizable usage rights (see icapmanage -x). This option is ignored if the -b option is also specified.
running iCAP software, the unreachable partition may be assumed to be using all cores on cells configured for that partition. Because of this, cells in partitions from which usage rights have been acquired should be rebooted or made inactive within 12 hours. If this is not done, the partition can begin to consume temporary capacity. If temporary capacity is not available, the complex might no longer be in compliance with the iCAP contract.
To avoid this problem, usage rights must be restored (using the -z option) before failback. -z Restore previously seized core usage rights to the nPartition containing the specified host. Core usage rights must be available in the GiCAP group or the command fails.
standby Group Manager and all member hosts has been previously established before the use of the icapmanage -Q command. Normally this occurs automatically when adding a new member to a group, updating the host list for an existing member, or adding a standby Group Manager. This command can be issued on an active Group Manager. In this case, the active Group Manager continues as the active Group Manager.
A standby Group Manager can be added anytime after the active Group Manager has grouping rules installed on it (before or after the application of sharing rights to the active Group Manager, before or after groups are created). A Group Manager in standby status can be removed at any time. -T [,]... -U Test hardware compatibility for one or more host systems in order to determine which groups the systems can join.
inactive because usage rights have not been purchased. Number of inactive This field displays the actual number of inactive cells: cells across the group. It does not include counts for inactive cells associated with inaccessible members (no partitions could be contacted). Amount of memory This field displays the total amount of memory without usage rights: which must remain inactive across all group members because usage rights have not been purchased.
Seized core usage rights: Expiration of seized core usage rights: of usage rights that are not in use. This field is displayed only when the -v option is specified. This summary field displays the number of expiring core usage rights that were seized from inaccessible members (see icapmanage -x). This field is displayed for all status options (-s, -b, -v), but only when usage rights were seized from member systems where none of the partitions could be contacted.
but the group total for number of cores without usage rights includes last-known values for unreachable members. Additionally, information about rights seizure can be displayed for members where none of the partitions can be contacted: Seized core usage rights: Expiration of seized core usage rights: This summary field displays the total number of expiring core usage rights that were seized from all partitions of this member (using icapmanage -x operations when none of the partitions could be contacted).
Expiration: were seized for disaster recovery, if none of the member partitions could be contacted. This field displays the expiration date for core usage rights that were seized with icapmanage -x operations from the preceding named partition, or from the complex in the case of unassigned usage rights. The expiration date for a rights seizure operation effectively terminates the period during which the core usage rights are available to other group members for purposes of disaster recovery.
International Code Set Support Single- and multiple-byte character code sets are supported. RETURN VALUE icapmanage exits with one of these values: Command succeeded. 0 >0 Command failed; error message sent to STDERR. FILES Log file for GiCAP operations and messages. Encrypted file containing grouping rules used by the Group Manager. Encrypted file containing information about /etc/opt/iCAP/GiCAP_db sharing rights and information about each group managed by the Group Manager.
icapmanage -a -S mystandby.node.hp.com Remove host mystandby from use as a standby Group Manager: icapmanage -r -S mystandby.node.hp.com Take control as an active Group Manager: icapmanage -Q Show the full status of the ADMIN1 group: icapmanage -s -g ADMIN1 -v Seize core usage rights from a partition that is unavailable to make them available to other group member activations: icapmanage -x mypar1.node.hp.
icapmodify(1M) NAME icapmodify -- Activate and deactivate cores. Specify system contact email address. Change Instant Capacity configuration information. Specify Instant Capacity from email address. Specify system identifier. Specify temporary capacity warning period. Apply codewords.
Intended Active Changes to the number of intended active cores through the use of this command are persistent (survive system reboot). The intended active number is the number of cores that the Instant Capacity software attempts to activate at system boot time. It is adjusted by use of the -a, -d, and -s options. The number of intended active cores for each partition is displayed using the icapstatus command (see icapstatus(1M)).
-D it deassigns the specified number of cores from the local vPar. Defers a core activation or deactivation until the next reboot. This option modifies the default behavior of the -d, -s, and -a options, which is to activate or deactivate cores instantly. NOTE: This option is not supported within a virtual partition. Deferred operations are not cumulative.
works exactly as the -a option (if n is greater than the current number of active cores), or exactly as the -d option (if n is less than the current number of active cores). Specifying a value of n less than the number of cells in a partition will fail. In a virtual partition environment, if unused capacity is not available, this option will use the value of n as the desired number of cores to be active in the local virtual partition.
only option that can be used when the complex is in this state is the -C option, which accepts the upgrade codeword. EXTERNAL INFLUENCES Environment Variables • • • • LANG determines the locale to use for the locale categories when both LC_ALL and the corresponding environment variable (beginning with LC_) do not specify a locale. If LANG is not set or is set to the empty string, a default of “C” is used (see lang(5)). LC_CTYPE determines the interpretation of single- and multiple-byte characters.
icapmodify -f admin@research.corp.com Set the system_id to Asset_Num_234: icapmodify -i Asset_Num_234 Set the system contact email address to super_user@corp.com: icapmodify -c super_user@corp.com AUTHOR icapmodify was developed by HP. SEE ALSO icapnotify(1M), icapstatus(1M), icapmanage(1M), icapd(1M), icap(5), vparmodify(1M).
icapnotify(1M) NAME icapnotify -- Test email connectivity to HP for Instant Capacity (iCAP) systems. Request a confirmation response email from HP. Turn configuration change notification and asset reporting on or off.
International Code Set Support Single- and multiple-byte character code sets are supported. RETURN VALUE The icapnotify command exits with one of these values: Command succeeded. 0 >0 Command failed; error message sent to STDERR. EXAMPLES Test email connectivity with HP by sending an asset report to HP, root, and super_user@corp.com, and request a confirmation email from HP to be sent to super_user@corp.com: icapnotify super_user@corp.
icapstatus(1M) NAME icapstatus -- Display Instant Capacity (iCAP) status and system information. SYNOPSIS icapstatus icapstatus -s Deprecated: icod_stat icod_stat -s DESCRIPTION The icapstatus command displays Instant Capacity status and configuration information, counts, status, and allocation of Instant Capacity components (cores, memory, and cells) for an Instant Capacity system.
exception reports for the local system. This field is set via the icapmodify -c command. From email: This field displays the email address that will be specified as the sender of all Instant Capacity initiated email correspondence for the local system. This field is set via the icapmodify -f command. If not set, email will be sent from the adm user on the local system.
Borrowed/Loaned memory usage rights: This field identifies the count of memory usage rights that were either borrowed from or loaned to the GiCAP group. This value must be 0 in order to remove the member from the GiCAP group. The output of icapstatus reflects the results of any GiCAP group operations: the borrowing or loaning of component usage rights or the transfer of temporary capacity.
Number of cores currently unavailable for assignment: GiCAP group), even if the -t option is used with icapmodify for an activation. This field displays the number of unassigned cores in the hard partition that are not assigned to the local virtual partition and cannot be instantly assigned. This number includes cores in inactive cells and deconfigured cores. When using versions of vPars before A.03.
inactive cores in a partition using temporary capacity. Also, temporary capacity is not used as long as there are available core usage rights on the complex, even if the -t option is used with icapmodify for an activation. This information is not displayed on a virtual partition. Number of cores that are This field displays the number of cores that cannot be deconfigured or attached to inactive activated by Instant Capacity software.
Allocation of Instant Capacity Resources Among the nPartitions The following table displays how Instant Capacity components are distributed among the partitions in the complex: nPar ID: Total cores: Intended active cores: Actual active cores: Inactive cores: Inactive memory: Inactive cells: Runs iCAP: nPar name: This field displays the partition number for the row of data. This field displays the total number of cores physically present for the hard partition.
2 >0,!=2 Command succeeded; system is not an Instant Capacity system. Command failed; error message sent to STDERR. AUTHOR icapstatus was developed by HP. SEE ALSO icapmodify(1M), icapnotify(1M), icapmanage(1M), icapd(1M), icap(5).
icapd(1M) NAME icapd -- Instant Capacity (iCAP) daemon. SYNOPSIS icapd DESCRIPTION The icapd (formerly icodd) daemon is installed and started as part of the Instant Capacity software on all potential iCAP systems, and respawns itself if killed. If this daemon is not running, other Instant Capacity commands fail. The operations this daemon performs are vital in keeping the complexwide view of the Instant Capacity state current.
A Special Considerations This appendix covers the following topics: • “Assumed Values in icapstatus Command” (page 184) • “Upgrading to Instant Capacity version B.06.
A.1 Assumed Values in icapstatus Command The icapstatus command might make assumptions on the number of active cores and amount of active memory, depending on certain system conditions. If values are assumed, the icapstatus command output contains an asterisk next to the appropriate field. A.1.
A.2 Upgrading to Instant Capacity version B.06.x or later (HP-UX) The first time a version of the codeword-based B9073BA Instant Capacity software (B.06.00 or later) is loaded onto a system where the old B9073AA software (version B.03.x through B.05.x) has been in use, the new software requires the system to go through an upgrade process. This process involves transferring Instant Capacity inventory information from HP to the system through the application of an upgrade codeword.
7. Execute the following command: /usr/sbin/icod_stat 8. 9. Inspect the icod_stat command output for the line that indicates the Exception status (near the top of the output). If it displays “No exception”, your system is in compliance. Inspect the remainder of the output to see the distribution of your active and inactive cores in the system and, if you want to make changes, modify it using the /usr/sbin/icod_modify command.
A.3 Dual-Core Support in Instant Capacity Systems Each HP cellular complex has 4 sockets. With dual core processing, each socket accepts a CPU module that contains 2 processor cores. You can upgrade an Instant Capacity Superdome system to a dual-core system by replacing the cell boards and processors. Contact your HP service representative for details on upgrading to dual core processors. The Instant Capacity software supports dual core processors.
A.4 New Partition Creation and Instant Capacity You can assign a cell to an existing partition even if the cell contains cores without usage rights (Instant Capacity processors), as long as there are enough available core, cell, and memory usage rights to cover activation of the cell, its memory, and at least one of the cores on the cell.
A.5 Implications of Removing a Cell from an Instant Capacity System The Instant Capacity software tracks the expected number of inactive components (cores, cells, and memory) in a complex and knows the actual number of active and inactive components. The complex is in compliance if the actual number of inactive components meets or exceeds the expected number of inactive components.
A.6 Shutting Down a Partition with Instant Capacity Cores The Instant Capacity software saves information about the number of active cores for each partition, and this information expires over time. If the partition is not active (but the hardware is powered up), Instant Capacity software on other partitions assumes that all cores in the inactive partition are active unless it can detect otherwise. For details about these assumed processor values, see “Assumed Values in icapstatus Command” (page 184).
A.7 Instant Capacity and Reinitializing the nPartition (Genesis Partitions) Any use of the CC command at the service processor level has the potential to overwrite the Instant Capacity configuration, and is therefore not recommended on Instant Capacity systems. In particular, creating a Genesis Partition on an Instant Capacity system is not recommended because it causes the system to be out of compliance.
A.8 par Commands from PC System Management Station Use of par commands (such as parmodify or parcreate) can cause changes to a complex that affect the Instant Capacity state of the complex. Therefore, if a par command is executed on an Instant Capacity complex from a PC System Management Station (SMS), the command must be directed towards a HP-UX partition in order to succeed so that the Instant Capacity software can authorize the change. The par commands support this functionality through the -h option.
A.9 Instant Capacity Compatibility with Processor Sets (HP-UX) A.9.1 Overview The Instant Capacity software successfully coexists with processor sets (psets). To coexist with psets, the Instant Capacity software activates and deactivates cores in only the default processor set. Cores in nondefault processor sets are not activated or deactivated. NOTE: There must be at least one core in the default processor set. The last remaining core in the default processor set is unavailable for deactivation. A.9.
A.10 Configuring Email on Instant Capacity Systems A.10.1 Email Requirements Previous versions of the Instant Capacity software required email connectivity to HP in order to send asset reports as encrypted email messages. Starting with version B.07.x, Instant Capacity software does not require email connectivity or asset reporting. However, you can choose to configure it because it can be useful for viewing complex-wide asset information at the HP Utility Pricing Solutions portal.
system is on an isolated network, email from the system does not reach HP. This causes your system to be out of compliance with your Instant Capacity contract if you are using temporary capacity (TiCAP). The sendmail application The sendmail application is used by the Instant Capacity software to send encrypted email messages from your system to HP. The sendmail daemon, if running, can also be used to receive email. For purposes of this email configuration, only the ability to send email is required.
• • The Instant Capacity system is not advertised to the internet, but hostname mycompany.com is advertised and reachable from the internet. Email is forwarded from the system to a mail relay host called mailhub. The mail server called mailhub can either be directly connected to the internet and send the email directly to HP, or it can forward the email to another mail server on its way to HP. NOTE: Any bounced Instant Capacity email messages are sent to the adm mailbox. A.10.1.
A.10.1.4 Configuring Your Server to Send but Not Receive Email For security reasons, some organizations do not allow incoming mail. If you want your Instant Capacity system to only send email but not receive email, complete the following configuration procedure: 1. To prevent the sendmail daemon from starting up again when your system reboots, edit the /etc/rc.config.d/mailservs file, and change the value of SENDMAIL_SERVER to 0: vi /etc/rc.config.
A.11 Measurement Software and Instant Capacity Systems Systems with Instant Capacity components (and systems contributing usage rights to Instant Capacity systems) might have fewer active cores than the total number of cores in the system. This fundamental difference between the number of active cores and the total number of cores can cause some processor measurement products and utilities to report incorrect information.
A.12 Dynamic Processor Resilience (HP-UX) The LPMC monitor, within the Support Tools Manager (STM) diagnostics, generates Information events for all cache errors that are detected. After three errors (Threshold) are detected on a processor in 1440 minutes, or a 24-hour period of time (Period), the monitor deactivates that particular processor, marks it for deconfiguration on the next system reboot, and generates a Serious event.
A.13 Security Issues A.13.1 Customer protections which iCAP assumes to be in place Instant Capacity commands provide system status information and facilitate system configuration modification, and are therefore executable only by users with root level access. An assumption is made that there exist administrative policies which exercise the appropriate degree of control over root level access. A.13.
B Considerations for OpenVMS Systems This appendix covers the following topics: • “CLI Support on OpenVMS” (page 202) • “DCL Commands” (page 204) • “Special OpenVMS-Specific Features and Considerations” (page 212) • “Restrictions” (page 213) 201
B.1 CLI Support on OpenVMS OpenVMS provides a CLI (command-line interface) to the Instant Capacity software. The HP-UX command syntax can be implemented using foreign command symbols. The DCL ICAP command provides DCL command support. B.1.1 HP-UX Style Commands The HP-UX command syntax can be used on OpenVMS systems by defining foreign command symbols to the iCAP images. Add the following three symbol declarations to your LOGIN.
Table B-1 HP-UX and OpenVMS Command Equivalents (continued) HP-UX Style OpenVMS Style icapmanage -R [[,]...] icap manage report [-U ] icapmanage -x icap manage extract B.1.3 OpenVMS iCAP Files Table B-2 lists the files that are new to iCAP version 8.1 on OpenVMS. Table B-2 OpenVMS iCAP Files OpenVMS File Location HP-UX File Location Supplied By sys$manager:GiCAP.log /var/adm/GiCAP.log Created at run time. sys$system:GiCAP.
B.1.4 DCL ICAP Command The ICAP command supports six command options to perform iCAP operations on OpenVMS systems. B.2 DCL Commands B.2.1 ICAP ACTIVATE Name ICAP ACTIVATE - Immediately activates additional cores on the system. (HP-UX equivalent: icapmodify -a) Format ICAP ACTIVATE /CPU=n [/DEFER] [/TICAP] Qualifiers /CPU=n [/DEFER] [/TICAP] 204 Specifies the number of additional cores to activate. This qualifier is required. Defers the activation until the next reboot.
B.2.2 ICAP APPLY Name ICAP APPLY - Apply an iCAP codeword. (HP-UX equivalent: icapmodify -C) Format ICAP APPLY "codeword" Parameter "codeword" An iCAP codeword obtained from the HP Utility Pricing Solutions portal. Enclose the codeword in double quotation marks. B.
B.2.3 ICAP DEACTIVATE Name ICAP DEACTIVATE - Deactivates cores on the system. (HP-UX equivalent: icapmodify -d) Format ICAP DEACTIVATE /CPU=n [qualifiers] Qualifiers /CPU=n /DEFER 206 Specifies the number of cores to deactivate. This qualifier is required. Defers the deactivation until the next shutdown.
B.2.4 ICAP RECONCILE Name ICAP RECONCILE - Activates or deactivates cores (subject to compliance limits) to bring the system to a state where the intended active number of cores are active. (HP-UX equivalent: icapmodify -r) Format ICAP RECONCILE B.
B.2.5 ICAP SET Name ICAP SET - Sets various iCAP management variables. Format ICAP SET parameter [qualifiers] Parameters ACTIVE_CPU Sets the number of active cores and the number of intended active cores. (HP-UX equivalent: icapmodify -s) Format ICAP SET ACTIVE_CPU count Value count: the number of cores to set active in the npartition. ASSET Sets the asset reporting email on or off.
Value id: A user-defined string to identify this system when tracking or reporting usage. Specify a null string ("") to set the system ID to the default value. The default value is the local hostname. WARNING_DAYS Sets the temporary capacity warning period to the number of days specified. (HP-UX equivalent: icapmodify -w) Format ICAP SET WARNING_DAYS days Value days: the number of days of temporary capacity before temporary capacity expiration warning email is sent to the system contact. B.
B.2.6 ICAP SHOW Name ICAP SHOW - Show the status and settings of the iCAP software on the OpenVMS system. (HP-UX equivalent: icapstatus) Format ICAP SHOW STATUS [qualifiers] Parameter STATUS Show the iCAP status and system settings to the standard output device. Qualifiers /SNAPSHOT 210 Creates a string of snapshot information containing encrypted audit data and displays the string to the standard output device.
B.2.7 ICAP_SERVER Name ICAP_SERVER - iCAP server process. Description The ICAP_SERVER process performs the same functions as the icapd daemon process on HP-UX systems. For more information, see the HP-UX icapd manpage. To ensure compliance, the ICAP_SERVER is always running on OpenVMS systems in an iCAP complex. B.
B.3 Special OpenVMS-Specific Features and Considerations B.3.1 Core Activation and Deactivation Unlike HP-UX, the OpenVMS operating system provides a user interface to start and stop system processor resources. When you enter the START /CPU command on an OpenVMS system in a complex containing iCAP resources, the ICAP_SERVER process validates that the start operation does not take the complex out of compliance.
B.4 Restrictions • • • • Instant Capacity software on OpenVMS Version 8.3-1H1 does not support HP virtual partitioning (vPars). Global Instant Capacity features, including the use of the icapmanage command, are not supported on OpenVMS. Instant Capacity on OpenVMS does not support internationalization. Only English language support is provided. LPMC and HPMC are not available on OpenVMS systems. B.
Glossary activate cell The process of changing an inactive cell into an active cell. A cell is added to a partition using the parmodify and parcreate commands, and is activated through a reboot or reconfig, or through cell online activation. activated core A core that has been turned on by the Instant Capacity software or during installation. Cores are activated with the icapmodify command (or the vparmodify command in an HP-UX virtual partition) while HP-UX or OpenVMS is running.
enable the creation of one or more groups (GiCAP codewords). Codewords are purchased from HP and retrieved from the Utility Pricing Solutions Portal. See also RTU, sharing rights, usage rights. configured processor A processor that is configured at the boot console handler (BCH or EFI) and whose cores are now available for activation by the Instant Capacity software. core The actual data-processing engine within a processor.
• Boot-is-blocked. • The cell is assigned to an nPartition. See also active cell. inactive core A core that either has not yet been activated or that has been turned off by the Instant Capacity software and returned to the pool of inactive cores. Inactive cores are available for activation.
monarch processor Also known as the boot processor. The main controlling core of the operating system. This core is designated as CPU 0. The LPMC monitor does not deactivate or replace a failing monarch processor. nPartition Also known as a hard partition. A partition in a cell-based server that consists of one or more cells and one or more I/O chassis.
sharing rights A type of codeword applied to a Group Manager to enable the addition of members with Instant Capacity components to groups. To share resources across groups, you must purchase GiCAP sharing rights, acquire the GiCAP codeword from the HP Utility Pricing Solutions Portal (http:// www.hp.com/go/icap/portal), and apply the associated codeword to the Group Manager system.
VM Host A server running software such as HP Integrity Virtual Machines, VMware ESX, or Microsoft Virtual Server, that provides multiple virtual machines, each running its own instance of an operating system. vPars An HP software product that provides virtual partitions. See also virtual machine, virtual partition. WBEM Web-Based Enterprise Management. A set of web-based information services standards developed by the Distributed Management Task Force, Inc. A WBEM provider offers access to a resource.
Index A activating cores, 55 virtual partition environment, 62, 63 Administration System, 22 asset report testing email transmission, 197 assigning cell to partition, 65 assumed values in icapstatus command, 184 audit application, 22 B boot time compliance, 64 boot time enforcement, 36 C cell assigning to partition, 65 unassigning from partition, 67 cell boards, 31 activating, 38, 90 cell removal implications, 189 cimconfig command, 44 cimserver command, 44 codewords, 34 applying, 29, 34, 53 TiCAP, 35 com
WBEM requirements, 102, 126 Global Instant Capacity (see GiCAP) grouping rules, 33 H high availability, 100, 122 HP OpenView measurement software, 198 HP-UX reinstalling, 46 HP-UX 11i v1 requirements, 26 HP-UX 11i v2 requirements, 27 HP-UX 11i v3 requirements, 28 HPMC core failure and replacement, 71 I IAC (see Instant Access Capacity) ICAP_SERVER time zone, 42 icapd daemon time zone, 42 icapmanage command, 103 adding group members, 107 adding partitions, 119 creating groups, 107 installing grouping rules
ICAP ACTIVATE command, 204 ICAP APPLY command, 205 ICAP DEACTIVATE command, 206 ICAP RECONCILE command, 207 ICAP SET command, 208 ICAP SHOW command, 210 ICAP_SERVER process, 211 restrictions, 213 special features and considerations, 212 system files, 203 OpenVMS considerations, 201 OpenVMS requirements, 28 overriding deferred activation, 59 overriding deferred deactivation, 59 P par commands with PC System Management Station, 192 parmodify command, 55 partitions shutting down, 55, 190 patches for HP-UX 11i
email configuration, 133 Instant Capacity software, 131 U unassigning cell from partition, 67 unused capacity, 62 upgrades GiCAP, 119 Instant Capacity version B.06.
