HP Instant Capacity User's Guide for Versions 8.
© Copyright 2000-2007 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.............................................................................................................15 Intended Audience................................................................................................................................15 New and Changed Information in This Edition...................................................................................15 Publishing History.......................................................................
Temporary Instant Capacity (TiCAP)...................................................................................................38 Instant Capacity Compliance and Enforcement...................................................................................39 Configuration Change Notification......................................................................................................40 Core Activation..............................................................................................
Temporary Instant Capacity Exceptions...............................................................................................83 Error for Activation with Insufficient Temporary Capacity............................................................83 Temporary Capacity Balance Needing Action................................................................................83 Temporary Capacity Negative Balance...........................................................................................
Global Instant Capacity.......................................................................................................................134 1 Instant Capacity HP-UX Manpages.........................................................................135 iCAP(5)................................................................................................................................................136 icapmanage(1M)......................................................................................
HP-UX Style Commands...............................................................................................................194 OpenVMS Command Mapping.....................................................................................................194 OpenVMS iCAP Files.....................................................................................................................195 DCL ICAP Command..............................................................................................
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 Instant Capacity System Elements................................................................................................25 Permanent Activation of Instant Capacity Components..............................................................58 Partition pre-modification state: One cell assigned with 3 active and 1 inactive cores, and available usage rights for 2 additional cores..............................................
List of Tables 1 1-1 6-1 6-2 9-1 9-2 A-1 A-2 B-1 B-2 Publishing History Details............................................................................................................16 Most Recent Instant Capacity Versions and Supported Platforms...............................................27 Cell Board Activation Not Requiring Additional Core Usage Rights..........................................92 Cell Board Activation Requiring Additional Core Usage Rights.........................................
List of Examples 2-1 4-1 4-2 4-3 4-4 4-5 4-6 5-1 5-2 5-3 5-4 5-5 5-6 5-7 6-1 6-2 6-3 6-4 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 8-1 8-2 8-3 8-4 A-1 A-2 A-3 Configuration Change Notification E-Mail for (non vPar) Instant Capacity System...................40 Sample Session of icapstatus (on HP-UX).....................................................................................55 Applying an RTU Codeword (HP-UX).........................................................................................
About This Guide The HP Instant Capacity User’s Guide for Versions 8.x provides you with the most recent information for using the Instant Capacity version 8 software. This document describes Instant Capacity version B.11.31.08.03.00 on HP-UX 11i v3 systems, B.11.23.08.03.00 on HP-UX 11i v2 systems, B.11.11.08.03.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 versions 8.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.
Typographic Conventions This document uses the following conventions. audit(5) Book Title KeyCap Emphasis Bold Bold ComputerOut UserInput Command Variable [] {} ... | 18 An HP-UX manpage. In this example, audit is the name and 5 is the section in the HP-UX Reference. On the web and on the Instant Information media, it may be a hot link to the manpage itself. From the HP-UX command line, you can enter “man audit” or “man 5 audit” to view the manpage. See man(1). The title of a book.
Instant Capacity Information Instant Capacity User’s Guide History This is the fifth edition of the HP Instant Capacity User’s Guide for Versions 8.x. Locating the Instant Capacity User’s Guide for Versions 8.x You can find the HP Instant Capacity User’s Guide for Versions 8.
Manpages NOTE: The information contained in this section applies only to HP-UX systems. It does not apply to Integrity servers running OpenVMS.
1 Instant Capacity Overview This chapter covers the following topics: • “Introduction” (page 22) • “Overview” (page 24) For more in-depth information, see the HP-UX manpage icap(5).
Introduction Welcome Welcome to the HP Instant Capacity User’s Guide for versions 8.x. Hewlett-Packard’s Instant Capacity software product provides the ability to instantly increase or decrease computing capacity on specified HP enterprise servers. NOTE: The name of the product has changed from Instant Capacity on Demand (or iCOD) to HP Instant Capacity for HP 9000 and HP Integrity Servers, also known as Instant Capacity or iCAP.
IMPORTANT: It is always a good idea to keep some quantity of temporary capacity in reserve. Purchase of codewords may take one or more days, so having a buffer of temporary capacity allows you to avoid delays in activation of additional cores. The Instant Access Capacity provides this buffer initially, but as that capacity is depleted, ongoing purchases of additional Temporary Instant Capacity are recommended to replenish this capacity.
Overview Software Product Overview The Instant Capacity versions 8.x software products associated with HP’s Utility Pricing Solutions program are: • iCOD: HP product number B9073BA (HP-UX) • iCAP: HP OpenVMS product number BA484AA Only versions 8.x information is in this user’s guide. 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.
• • Monitor and report system compliance (icapd daemon on HP-UX, ICAP_SERVER process on OpenVMS) Manage Global Instant Capacity groups (icapmanage command) See “Instant Capacity HP-UX Manpages” (page 135) for details of these commands on HP-UX. See “DCL Commands” (page 196) for the OpenVMS equivalents of these commands. Utility Pricing Solutions Portal The Utility Pricing Solutions (or Instant Capacity) portal is located at the HP web site: http://www.hp.
Most Recent Instant Capacity Product Versions and Supported Platforms 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.08.03.00 (B9073BA) Supported Hardware Platforms Notes hp Integrity servers: • Superdome • rx8640 • rx8620 • rx7640 • rx7620 Available on: • http://www.hp.com/go/softwaredepot • December 2007 HP-UX 11i v3 Applications Software media hp 9000 servers: • • • • • • • iCOD HP-UX 11i v2 B.11.23.
Past Instant Capacity Versions and Supported Operating Systems Previous versions of the Instant Capacity software are: • 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 30) • “Instant Capacity Components” (page 34) • “Instant Capacity Codewords” (page 37) • “Instant Capacity Compliance and Enforcement” (page 39) • “Configuration Change Notification” (page 40) • “Core Activation” (page 41) • “Temporary Instant Capacity (TiCAP)” (page 38) • “Instant Capacity Cell Board” (page 42) • “Instant Capacity Software Validation” (page 43) • “Instant Capacity System Status Reporting” (p
Instant Capacity Requirements Program Requirements You must comply with the following HP Utility Pricing Solutions conditions to participate in the Instant Capacity versions 8.
• • • • • • • PHKL_25218: fix PHKL_26232: PHKL_30197: PHCO_24396: PHCO_24477: PHCO_29832: PHCO_29833: S700_800 11.11 PDC Call retry, PDC_SCSI_PARMS, iCOD hang S700_800 S700_800 S700_800 S700_800 S700_800 S700_800 11.11 Psets Enablement patch,FSS iCOD patch 11.11 Psets & vPar, Reboot hangs, serial number 11.11 /etc/default/tz patch 11.11 sar (1M) patch 11.11 reboot(1M) patch 11.
□ □ If you have a virtual partitioned environment, the Virtual Partitions software (bundle T1335BC) must be version A.05.01 or greater. vPars is available separately and is not included with the OE. (GiCAP only) Secure Shell bundle, distributed with the Operating Environment, although a newer version may be available from the HP software depot (http://www.hp.com/go/softwaredepot) OpenVMS 8.3-1H1 Requirements The following software is required for Instant Capacity versions 8.x on OpenVMS 8.
Usage Rights Requirement A system managed under the Instant Capacity program may include one or more components (core, cell, or memory) that are without usage rights. Before you can use these components, additional usage rights must be obtained. Usage rights can either be purchased from HP, or if the system is a member of a Global Instant Capacity group, usage rights may be temporarily borrowed from another member of the group, as described in the section “Global Instant Capacity Sharing Rights” (page 103).
Instant Capacity Components 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 complex-wide database of usage rights. See “Usage Rights Requirement” (page 33) for details about acquiring additional usage rights. Activation of components is restricted according to complex-wide 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. IMPORTANT: You must have one active core for each active cell board. Memory As with other components, the Instant Capacity software enforces compliance for memory by comparing the amount of actual inactive memory with the expected inactive memory, which is the amount of memory without usage rights for the entire complex.
Global Instant Capacity Global Instant Capacity, or GiCAP, provides HP customers with the flexibility to move usage rights (RTUs) 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.
Instant Capacity Codewords Instant Capacity uses codewords for several purposes: to adjust available usage rights for system components (RTU codewords), to apply an amount of 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.
Temporary Instant Capacity (TiCAP) 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.
Instant Capacity Compliance and Enforcement The Instant Capacity software primarily maintains complex-wide 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, then the software also maintains group-wide information about usage rights. See Chapter 7 for more information about GiCAP.
Configuration Change Notification Specifying an increase or decrease in the number of active cores — using the icapmodify command — causes a core configuration change. A notification e-mail is sent to the system-contact when a change occurs that affects the configuration of cores.
Core Activation As previously mentioned, 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 may have fewer active components than they have rights to activate. Such systems may instantly activate additional components without the need to purchase an RTU, up to the number of component usage rights on the system.
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, additional cell and memory usage rights can be purchased and 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 (without usage rights) throughout the complex.
Instant Capacity Software Validation 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.
Instant Capacity System Status Reporting You can use the icapstatus command to view the status of your Instant Capacity system.
Timezone Considerations On HP-UX systems, the icapd daemon performs routine Instant Capacity software tasks on a daily basis. A partition’s local timezone setting affects what timezone the icapd daemon uses for the timing of these tasks, so you should ensure that the timezone is set properly to ensure synchronization among the partitions. Because the HP-UX icapd daemon is started by init, the /etc/default/tz file needs to contain the desired timezone specification.
3 Installing and Uninstalling Instant Capacity Software This chapter covers the following topics: • “Installing Instant Capacity Software” (page 48) • “Reinstalling Instant Capacity Software” (page 50) • “Uninstalling Instant Capacity Software” (page 51) 47
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. You can use the following HP-UX command to verify that the software is installed and configured: /usr/sbin/swverify iCOD You should see Verification succeeded. in the output of the swverify command.
For All HP-UX Installations After you have successfully installed the Instant Capacity software using the swinstall command, perform the following procedure to validate your installation: 1. 2. Execute the command: /usr/sbin/icapstatus Verify that the icapstatus command’s output indicates the correct number of components without usage rights for cells, cores, and memory. If any number is incorrect, contact your local HP Response Center and request iCAP assistance. 3. 4.
Reinstalling Instant Capacity Software 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”), all information in the Instant Capacity configuration file disappears unless you do the following: WARNING! If the system is a member of a Global Instant Capacity group, it should be removed from the group before reinstalling HP-UX, and added back into the group after t
Uninstalling Instant Capacity Software IMPORTANT: to remove it. The Instant Capacity software should not be uninstalled.
4 Using Instant Capacity to Manage Processing Capacity This chapter covers the following topics: • “Checking the Status of your Instant Capacity System” (page 54) • “Setting System-Contact Information” (page 56) • “Applying a Right To Use (RTU) Codeword” (page 57) • “Activating Cores” (page 59) • “Deactivating Cores” (page 61) • “Overriding Deferred Activations and Deactivations” (page 63) • “Load-Balancing Active Cores” (page 64) • “Assigning a Cell to a Partition” (page 65) • “Unassigning a Cell from a Pa
Checking the Status of your Instant Capacity System You can use the icapstatus command to view the status of your Instant Capacity system.
— — — Inactive Cells Runs iCAP (indicates whether the hard partition contains compatible Instant Capacity software) nPar Name See the icapstatus(1M) manpage for details of the icapstatus command and its output. 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.23.08.
Setting System-Contact Information It is recommended that you specify a system-contact’s e-mail address on each partition in your system. On OpenVMS systems, the e-mail address may be a logical pointing to a distribution list.
Applying a Right To Use (RTU) Codeword Unless you have a balance of Instant Access Capacity or temporary capacity (or usage rights available from a GiCAP group), additional usage rights must be acquired prior to activation of an inactive core. To purchase additional usage rights: 1. 2. 3. Contact your HP sales representative to purchase the appropriate Instant Capacity Right to Use (RTU) products. Acquire a Right to Use (RTU) codeword from the Utility Pricing Solutions web portal (located at http://www.hp.
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 58 Send Ack Letter Post IAC in iCAP DB Using Instant Capacity to Manage Processing Capa
Activating Cores The icapmodify command provides the ability to increase processing capacity instantly by activating cores with available usage rights in nPartitions (hard partitions) of 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. See “Instant Capacity Integration with Virtual Partitions (HP-UX only)” (page 179) for details about activation in virtual partitions.
NOTE: Instant Capacity will always consume unused capacity before it consumes additional usage rights when activating cores. Instant Capacity will always release usage rights from unused capacity before it releases usage rights by deactivating cores. Constraints The Instant Capacity software will not activate a core that is marked for deconfiguration. Also, you cannot use Instant Capacity to activate more cores than are configured in the current nPartition.
Deactivating Cores Deactivating Cores in nPartitions You have the ability to decrease processing capacity instantly on HP enterprise servers with the Instant Capacity software (even on servers with sufficient usage rights such that all cores can be simultaneously active). Any number of active cores can be deactivated at any time, within the partition constraints listed below. 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 the above deactivation example, the core deactivation is instant (that is, does not require a reboot). To defer the deactivation (until the next reboot) add the -D option to the command. See the HP-UX manpage icapmodify(1M) for details.
Overriding Deferred Activations and Deactivations NOTE: Only activation of cores is discussed in this section, but the discussion applies equally to the deactivation of cores. If you have performed a deferred core activation, using the -D option in the icapmodify 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.
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 under-utilized.
Assigning a Cell to a Partition A cell can be assigned to a partition only if there are sufficient cell usage rights 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 only by the partition to which the cell board is assigned. Cores on one cell board cannot be shared across multiple partitions.
Unassigning a Cell from a Partition When a cell is unassigned from a partition in a system with Instant Capacity, 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 post-modification state: Cell 3 is unassigned (total of 8 active is set) Cell 1 A A A Cell 2 A A A A A Figure 4-10 Post-modification state: Unassigned cell (Cell 3) with 4 inactive cores. The system has usage rights available for one 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 is changed from 9 to 8 (because 8 is the total number of cores remaining in the partition).
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, it may not recognize the newly activated core as available for processing.
Test Activation of Cores Using Temporary Capacity You may want to test your software application for proper operation and improved performance by activating an additional core. The use of temporary capacity (TiCAP) or Instant Access Capacity (IAC) is required for activation of a core without usage rights for testing purposes. See Chapter 5: “Temporary Instant Capacity” (page 73) for details. The following testing guidelines are meant to be an aid to your test plan.
Replacement of Failed Cores 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. See “LPMC Deactivations in Virtual Partitions” (page 183) for additional considerations in a virtual partition environment.
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) • “Tracking the Usage of Temporary Instant Capacity” (page 79) • “Temporary Instant Capacity Warning Period” (page 81) • “Temporary Instant Capacity Expiration and Compliance Enforcement” (page 82) • “Temporary Instant Capacity Exceptions” (page 83) 73
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 multiple processing-days. Temporary capacity allows one or more inactive cores to be activated for up to the specified period of pre-paid processing minutes, without requiring permanent usage rights for the cores.
IMPORTANT: Temporary Instant Capacity can only be used to activate Instant Capacity cores on a temporary basis. It cannot be used to activate Instant Capacity cell boards or Instant Capacity memory.
Ordering Temporary Instant Capacity To add temporary capacity credits to a system, order the desired quantity of the temporary capacity product for your type of server. The system serial number is required for orders of temporary capacity. Note that Instant Capacity cores that are added on to an existing system may include some additional temporary capacity called Instant Access Capacity (IAC).
Using Temporary Instant Capacity 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 capacity for your type of server by submitting a purchase order to HP. You must 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/07 08:00:00 NOTE: Temporary capacity cannot be used to activate Instant Capacity cores in inactive Instant Capacity cell boards. Additional usage rights must be purchased for the cell board, and perhaps also for the memory of the cell board.
Tracking the Usage of Temporary Instant Capacity The icapstatus command provides the following temporary capacity information: • • • Amount of temporary capacity remaining (in days, hours, and minutes) Number of cores using temporary capacity — this is the number of active cores without usage rights Projected temporary capacity expiration date and time — this is based on the current temporary capacity consumption rate You can find this information in the Instant Capacity Resource Summary section from the
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.
Temporary Instant Capacity Warning Period By default, the Instant Capacity software will send the expiration reminder when the temporary capacity balance is projected to expire within 15 days or less. You can adjust that warning period by specifying a different value with the icapmodify command, using the -w option. For example, this 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.
Temporary Instant Capacity Expiration and Compliance Enforcement IMPORTANT: If you leave cores without usage rights activated beyond the purchased temporary capacity duration, the software will automatically deactivate one or more cores on the next reboot of any partition in the complex. When you leave cores without usage rights activated on OpenVMS systems, the ICAP_SERVER will automatically deactivate one or more cores within one half hour on any partition in the complex.
Temporary Instant Capacity Exceptions 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 88) • “Ordering Instant Capacity Cell Board” (page 89) • “HP-UX and OpenVMS License and Support” (page 90) • “Acquisition of Usage Rights (RTU) for Instant Capacity Cell Board” (page 91) • “Instant Capacity Cell Board and Considerations of Core Usage Rights” (page 92) • “Activation of an Instant Capacity Cell Board” (page 93) • “Accidental Activation of an Instant Capacity Cell Board” (page 94) • “I
Instant Capacity Cell Board Overview Instant Capacity Cell Board offers you 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/cores.
Ordering Instant Capacity Cell Board To order the Instant Capacity Cell Board product you need to 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.
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 Right to Use (RTU) product, you must additionally pay for the incremental HP-UX or OpenVMS license and support costs 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 not included as part of the cell board RTU.
Acquisition of Usage Rights (RTU) 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 Right to Use (RTU) product for the cell board for your specific class of HP server. Order the appropriate HP Right to Use (RTU) product for the entire amount of Instant Capacity memory on the cell board.
Instant Capacity Cell Board and Considerations of Core Usage Rights There must be at least one core usage right available for an Instant Capacity cell board you wish to activate. Each active cell board must have at least one active core. However, this does not necessarily mean you must acquire additional core usage rights. No additional core usage rights are required unless the requirement of a minimum of one core per active cell board could not be met without acquiring additional core usage rights.
Activation of an Instant Capacity Cell Board An Instant Capacity cell board is usually assigned to an nPartition; however, it 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 Perform a reboot of the nPartition (using the shutdown -r command on HP-UX), or (on HP-UX 11.
Accidental Activation of an Instant Capacity Cell Board If you inadvertently activate an Instant Capacity cell board, you can de-activate it by following this two step procedure: 1. 2. Set the cell board’s use-on-next-boot flag to “n” (no) using the parmodify command Perform a reboot of the nPartition (this is not necessary if there was no reboot after the activation), or (on HP-UX 11.
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.
Instant Capacity Cell Board and Temporary Instant Capacity You can only activate cores on activated cell boards for which cell board usage rights have been acquired. This is true for both permanent activation of a core or a 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 contained in it.
7 Global Instant Capacity This chapter covers the following topics: • “Global Instant Capacity Overview” (page 98) • “Global Instant Capacity Requirements” (page 100) • “Global Instant Capacity Group Managers” (page 101) • “Global Instant Capacity Sharing Rights” (page 103) • “Global Instant Capacity Grouping Rules” (page 102) • “Creating Global Instant Capacity Groups” (page 104) • “Global Instant Capacity Resource Sharing” (page 107) • “Global Instant Capacity and Temporary Capacity” (page 110) • “Global
Global Instant Capacity Overview Global Instant Capacity, or GiCAP, provides HP customers with the flexibility to move usage rights (RTUs) for Instant Capacity components within a group of servers, and it also provides “pooled” temporary capacity across the group. This provides more 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 Add Member Systems to Group Create GiCAP Group Purchase GiCAP Sharing Rights Codeword Apply Grouping Rules on Group Manager Acquire Grouping Rules from Portal Apply Codeword on Group Manager Acquire Codeword from Portal Additional Capacity Needed on System A Excess Capacity on System B Deactivate Component(s) on System B Activate Component(s) on System A HP Send Ack Letter Process Order for Codeword Post GiCAP Order in iCAP DB Global Instant Ca
Global Instant Capacity Requirements In order to use Global Instant Capacity, all partitions on all servers in the group must be running Instant Capacity version 8 or later. The Group Manager must be an HP-UX system running Instant Capacity version 8.01.01 or later. In order to enable the Disaster Recovery features introduced in iCAP version 8.02, the Group Manager must be running iCAP version 8.02.
Global Instant Capacity Group Managers For each group, an HP-UX system must be designated as the Global Instant Capacity Group Manager. It is this system which maintains information about the group, group resources, and the grouping rules. icapmanage commands are intended to be invoked only on a Group Manager system. The Group Manager must be an HP-UX system running Instant Capacity version 8.01.01 or later software.
Global Instant Capacity Grouping Rules A Global Instant Capacity 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 to be in a group, but there are grouping rules defined by HP to specify the types of servers allowed to group together.
Global Instant Capacity Sharing Rights While GiCAP is part of Instant Capacity and is installed at the same time as iCAP, it is not enabled during installation. In order 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.
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 and -g options. Members are added by issuing the icapmanage command using the -a option, 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.
prompted for the root password for each specified host. The password is used only to establish an SSH authorization for secure communication and is not saved or stored. Example 7-4 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-5 Example Output of icapstatus on 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.23.08.03 node USR4020003 A6093A Z3e0ec8e078cd3c7b mjones@corp.com Set to the default ('adm') on period: 15 days No exception Member zoo6 in GiCAP group MyGroup, managed by node.corp.
Global Instant Capacity Resource Sharing Once a group has been established, Instant Capacity resources (core, cell board, memory usage rights, and temporary capacity) may be shared among all the members of the group. The sharing can occur in several ways: • • • • During creation of the group, some members may have unused usage rights so that by simply joining the group, additional usage rights are available for use by any member of the group.
component on a third member system needs to be activated, the usage rights made available by the deactivated component may be taken by the system using temporary capacity. In this case it may be necessary to use the “-t” option to icapmodify to activate the component on the third member system using temporary capacity. Status Reporting Usage rights and temporary capacity can sometimes be temporarily assigned to the Group Manager, which can result in difficulty interpreting some of the data from icapstatus.
Example 7-7 Cell/Memory Sharing In the following 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.
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”.
Temporary Capacity Prefetch Since 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 may prefetch an amount of temporary capacity from one or more member systems.
Global Instant Capacity Member Removal 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 appropriate system. There is no need to activate resources to reclaim loaned usage rights. When a member of a GiCAP group is removed, the reclaimed usage rights will be held by the Group Manager until they are claimed.
Group Member Reinstallation If a group member is reignited, you must perform the following to re-establish communication between the newly ignited group member and the Group Manager: icapmanage -a -m : -g Group Member Reinstallation 113
Group Manager Availability If the Group Manager becomes unavailable, management of the GiCAP Group will be unavailable until the Group Manager is restored or replaced. The GiCAP Group members will continue operating as isolated iCAP systems, using whatever usage rights and temporary capacity they had available when the Group Manager became unavailable. A GiCAP Group member using borrowed usage rights will be able to continue using those usage rights.
Upgrades and Global Instant Capacity Care must be exercised before upgrading or changing hardware 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.
Rights Seizure Use the icapmanage -x command to acquire core usage rights from a specified host to make them available to other group members, also known as rights seizure. The specified host must be known to the GiCAP Group Manager (it appears in the output of icapmanage -s) and not currently running. That and any other (vPar) hosts associated with the same hard partition are verified to be unreachable by the GiCAP manager. The icapmanage -x command will check with each known host on the hard partition.
member, the usage rights will automatically be restored (reassigned) to the member partition (or complex, in the case of unassigned seized rights) from which they were seized. However, note that if the seized usage rights have been redeployed to other members and are not released at the expiration time, the group may go out of compliance or temporary capacity may be used to maintain compliance.
Multiple Group Considerations You can create multiple GiCAP groups and they can be managed by the same Group Manager or by different Group Manager systems. A server complex can only be a member of a single GiCAP group at a time. In order to participate in a different group, it must be removed from one group before being added to the other group. Sharing Rights can never be transferred between two Group Manager systems.
Additional Considerations Systems which 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 and the Group Manager, 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 122) • “Troubleshooting the Instant Capacity Software” (page 125) • “Diagnosing E-mail Configuration” (page 127) 121
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) Not enough sharing rights (GiCAP) Hardware added which is incompatible with the group NOTE: Your system may be out o
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.
Example 8-2 Content of Exception Report for More Cells Active than Expected More cells active than expected 'More cells active than expected' means that the number of active cells across the complex exceeds the number of cell usage rights. To find out how many inactive cells are expected on the complex, run icapstatus and look at the global number of cells without usage rights.
Troubleshooting the Instant Capacity Software In the event 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, this can be done by entering the following command: /usr/sbin/swverify iCOD You should see Verification succeeded. in the output of the swverify command.
$ 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 listed above must be loaded. 8. 9. (HP-UX) Make sure par commands such as parstatus are working. For failures in virtual partitions, check the vPar commands such as vparstatus.
Diagnosing E-mail Configuration You can use the following steps to confirm the e-mail configuration or to aid in debugging the configuration: 1. 2. 3. 4. Send an e-mail message from your system to an e-mail address in the same domain (intranet) and confirm receipt of the e-mail message. Send an e-mail message from your system to an e-mail address outside of your domain (to the internet, for example, to a yahoo or hotmail e-mail address) and confirm receipt of the e-mail message.
9 Frequently Asked Questions This chapter covers frequently asked questions on the following topics: • “Instant Capacity Software” (page 130) • “Instant Capacity Hardware” (page 133) • “Global Instant Capacity” (page 134) 129
Instant Capacity Software What software product is required for Instant Capacity on Itanium-based servers running HP-UX 11i v2? The HP software bundle for the Instant Capacity versions 8.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 Pay per use and Instant Capacity software bundles are mutually exclusive.
How can I obtain codewords for newly purchased usage rights (RTUs) 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 versions 8.
Table 9-1 E-mail sent by the Instant Capacity software (continued) Triggered By E-mail Message vPars startup (when the virtual partition has Information about why the virtual partition is not being allowed to more cores assigned to it than the number of boot is sent to the system-contact, if specified, and root.
Instant Capacity Hardware Can a faulty cell board be replaced with an inactive Instant Capacity cell board? Yes. This is accomplished by first deactivating the failed cell board via the parmodify command and rebooting, followed by activating the inactive iCAP cell board and rebooting. In this situation, it is not necessary to obtain an RTU to activate the cell board.
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’s grouping rules, but no information on groups or group members is 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 iCAP version 8.02.
Instant Capacity HP-UX Manpages 135
iCAP(5) NAME iCAP -- Instant Capacity software for HP-UX and OpenVMS DESCRIPTION Instant Capacity provides services for instantly increasing or decreasing processing capacity (cores, cells, and memory) on supported HP servers to meet varying system demands. When the processing demand significantly changes, you can execute the icapmodify command (see icapmodify(1M)) to instantly activate or deactivate cores, or defer an activation or deactivation until the next reboot.
iCAP 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. After the appropriate codewords have been applied to a complex, additional components in the complex may be activated, up to the number of component usage rights granted by the applied codewords.
way to adjust capacity within virtual partitions of a single hard partition, but it does not affect the intended active count for the nPartition and it therefore cannot be used to migrate unused capacity either to or from other nPartitions. Note that with vPars version A.03.05 or greater, a compliance check is performed whenever a virtual partition is booted.
Note that whenever you have more active cores than the number of purchased core usage rights, the temporary capacity balance will be depleted as a mechanism for tracking the non-compliance of the system, and boottime deactivation of cores may occur even when TiCAP has not been purchased for the system. Instant Capacity Cell Board Instant Capacity Cell Board offers a way to have additional (inactive) cell board capacity for your system.
GiCAP Grouping Rules Once you have determined which system will host a Group Manager, you must acquire grouping rules from the portal and install the encrypted file on the Group Manager system using the icapmanage -i command. Under some circumstances you may need to acquire newer grouping rules from the portal (for example, when adding new hardware not covered by the grouping rules currently in use).
GiCAP Member Removal Before removing a member from a GiCAP group, all the borrowed usage rights must be returned and all outstanding loans reclaimed by deactivating resources on the appropriate system. There is no need to activate resources to reclaim loaned usage rights as the act of removing the member from a GiCAP group will reclaim the necessary usage rights.
Additional GiCAP Considerations Systems which 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 and the Group Manager, sufficient GiCAP Sharing Rights, and adherence to the GiCAP grouping rules are the only constraints.
icapmanage(1M) NAME icapmanage -- Global Instant Capacity (GiCAP) management commands for GiCAP groups.
Used in combination with the -u option in order to identify hosts to be added to or removed from an existing GiCAP group member's list. A hostlist identifies hosts to be added. A hostlist preceded by a ! identifies hosts to be removed. There must be no intervening blanks within a hostlist, and if both add and remove lists are specified, the entire string must be contiguous. Install a grouping rules file on a Group Manager system.
For a given command execution, host removals are processed before host additions. As a result, the same host may be removed and re-added with one update operation. With removes or adds applied, the resulting list must contain a representative host for each nPartition or virtual partition of the associated server. -v -x Provide verbose status information. Include all levels of information (group, manager and member).
made inactive within 12 hours. If this is not done, the partition may begin to consume temporary capacity. If temporary capacity is not available the complex may no longer be in compliance with the iCAP contract. Cells may be made inactive by removing them from the partition, shutting down the partition from within the OS by using shutdown -R -H, or with the MP RR command.
-R [[,]...] -T [,]... -U such as an RTU or TiCAP codeword.) For GiCAP Sharing Rights codewords, first, the GiCAP codeword must be purchased from HP. The number of rights purchased should equal or exceed the number of cores without usage rights for all planned members for all groups managed by the Group Manager. Next, the codeword should be retrieved from the HP Utility Pricing Solutions portal and applied to the Group Manager system.
vPar code (if any). This identification information is necessary when requesting a Sharing Rights codeword from the portal. Next it displays the number of Sharing Rights which have been purchased for this Group Manager, and how many Sharing Rights are currently in use versus the number still available to accommodate addition of new members or new groups with new members. Symbols used in the Display The output of an icapmanage -x command uses symbols next to the value of some fields in certain circumstances.
Temporary Capacity available: This field displays the amount of pooled group temporary capacity which is available to any member of the group. Projected temporary This field displays the date and time that capacity expiration: temporary capacity is projected to expire for the group at the present consumption rate. Temporary Capacity This field displays the total amount of balance: temporary capacity assigned to the group.
when usage rights have been released (or seized using icapmanage -x) from one member of a group, but have not yet been activated on another target member system. These values are displayed only when the -v option (verbose) is specified. Information Displayed This section is repeated for each member of the group, if the -b option for each Member of is not specified.
multiple expiration dates. To see the more detailed list of partition-specific rights seizure counts and expiration dates, use the -v option. Unassigned core usage This field displays the number of unused core rights seized: usage rights (not previously assigned to any partition) that have been seized from this member. This field is displayed only when the -v option is specified. Note that icapmanage -z can be used to restore core usage rights that were previously seized from partitions.
At the same time, the GiCAP software is concerned with the ability to transfer usage rights among members of the group. So, seizure of usage rights, borrows and loans of usage rights are described as “positive” counts of usage rights, such as “Number of core usage rights seized” and “Borrowed core rights”. The Group Manager also sometimes holds usage rights during transient states so all the Group Manager resources are described as positive counts of core usage rights.
/etc/opt/iCAP/.GiCAPKey, /etc/opt/iCAP/.GiCAPKey.pub product is installed after installation of Instant Capacity. Key files used by SSH for secure communication between the Group Manager and members of a group. EXAMPLES Install a new grouping rules file: icapmanage -i -U /tmp/GiCAP.rules Purchase a Sharing Rights codeword from HP with rights equal to or greater than the number of cores without usage rights for all planned members of the group.
icapmodify(1M) NAME icapmodify -- Activate and deactivate cores. Specify system contact e-mail address. Change Instant Capacity (iCAP) configuration information. Specify Instant Capacity from e-mail 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)).
-f -i -r -w -s -d, -s, and -a options, which is to activate or deactivate cores instantly. This option is not supported within a virtual partition. NOTE: deferred operations are not cumulative.
-t desc user_name Authorize use of temporary capacity. This option, in combination with either the -a or the -s option, specifies that a core activation is allowed to consume temporary capacity. Temporary capacity is consumed when the number of active cores exceeds the number of core usage rights. It is no longer used when the number of active cores is decreased to no more than the number of core usage rights available to the complex.
RETURN VALUE icapmodify exits with one of these values: Command succeeded. 0 >0 Command failed; error message sent to STDERR. FILES /var/adm/icap.
icapnotify(1M) NAME icapnotify -- Test e-mail connectivity to HP for Instant Capacity (iCAP) systems. Request a confirmation response e-mail from HP. Turn configuration change notification and asset reporting on or off.
International Code Set Support Single- and multi-byte character code sets are supported. RETURN VALUE icapnotify exits with one of these values: Command succeeded. 0 >0 Command failed; error message sent to STDERR. EXAMPLES Test e-mail connectivity with HP by sending an asset report to HP, root, and "super_user@corp.com", and request a confirmation e-mail 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 Obsolescent: 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.
System contact e-mail: This field displays the e-mail address for the person who should receive configuration change notification and exception reports for the local system. This field is set via the icapmodify -c command. From e-mail: This field displays the e-mail address that will be specified as the sender of all Instant Capacity initiated e-mail correspondence for the local system. This field is set via the icapmodify -f command. If not set, e-mail will be sent from the adm user on the local system.
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. The output does not take into account any component usage rights or temporary capacity that may be available on other GiCAP group members.
includes cores in inactive cells and deconfigured cores. When using versions of vPars before A.03.05, bound processors at the time the local virtual partition booted, if unbound later, cannot be instantly assigned to the local virtual partition without an intervening reboot (and assuming usage rights are available). Information displayed for the local nPartition The following status is displayed when icapstatus is run on a hard 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. This includes cores cells: in inactive cells, deconfigured cores, and failed cores deactivated due to LPMCs (Low Priority Machine Checks). This information is not displayed on a virtual partition.
Total cores: Intended Active cores: Actual Active cores: Inactive cores: Inactive Memory: Inactive Cells: Runs iCAP: nPar Name: This field displays the total number of cores physically present for the hard partition. This field displays the number of cores requested to be active for this hard partition; this is the number of cores that will be activated during a boot operation. Typically, this is the number that results from the execution of an icapmodify command.
SEE ALSO icapmodify(1M), icapnotify(1M), icapmanage(1M), icapd(1M), icap(5).
icapd(1M) NAME icapd -- Instant Capacity (iCAP) daemon. SYNOPSIS icapd DESCRIPTION icapd (formerly icodd) is installed and started as part of the Instant Capacity software on all potential iCAP systems, and re-spawns itself if killed. Note that other Instant Capacity commands fail if this daemon is not running. The operations this daemon performs are vital in keeping the complex-wide view of the Instant Capacity state current.
A Special Considerations This appendix covers the following topics: • “Assumed Values in icapstatus” (page 170) • “Upgrading to Instant Capacity versions B.06.
Assumed Values in icapstatus The icapstatus command may 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’s output contains an asterisk next to the appropriate field.
Upgrading to Instant Capacity versions 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. 8. 9. upgraded, the Instant Capacity software may determine the system to be in an exception state. Execute the following command:/usr/sbin/icod_statInspect 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 modify it using /usr/sbin/icod_modify if you want to make changes.
Dual Core Support in Instant Capacity Systems Each HP cellular complex has four sockets, and with dual core processing, each socket accepts a CPU module that contains two 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.
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.
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.
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. See “Assumed Values in icapstatus” (page 170) for details of these assumed processor values.
Instant Capacity and Re-Initializing 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.
par Commands from PC System Management Station (SMS) 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, in particular so that the Instant Capacity software can authorize the change.
Instant Capacity Integration with Virtual Partitions (HP-UX only) Overview Instant Capacity may 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).
Instant Capacity Integration with vPars — Supported Hardware Platforms Table A-2 Instant Capacity Integration with vPars — Supported Hardware Platforms Software and Version Operating System Version iCOD B.11.31.08.03.00 HP-UX 11i v3 (B9073BA) Supported Hardware Platforms Requirements hp Integrity servers: vPar software version A.05.01 or greater is required • Superdome • rx8640 Integrated virtual partition environment • rx8620 • rx7640 • rx7620 hp 9000 servers: • • • • • • • iCOD B.11.23.08.03.
Integrated Virtual Partition Environment Activation and Deactivation of Cores When using vPars, the icapmodify command must be used to modify processing capacity when you are making any adjustment to an nPartition or to multiple nPartitions: • When you execute the icapmodify command to deactivate a core, a check is made to see if the request can be satisfied.
icapmodify -d to stop the use of temporary capacity. It is not necessary to use the “-t” option when using the “-d” option. Example Output of icapstatus on a Partitionable System Containing vPars > /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.23.08.03 zoo6 USR4020003 A6093A Z3e0ec8e078cd3c7b mjones@corp.
Static Virtual Partitions If a virtual partition is static (that is, the resources cannot be migrated, added, deleted, or modified) and you attempt to activate or deactivate cores, the Instant Capacity software displays a message indicating that the configuration cannot be modified. NOTE: The icapstatus command’s output indicates that the number of cores that can or could be assigned (to the local virtual partition) is zero if the static resource attribute for the local virtual partition is set.
Instant Capacity Compatibility with Processor Sets (HP-UX) Overview The Instant Capacity software successfully co-exists with processor sets (Psets). To co-exist with Psets, the Instant Capacity software only activates and deactivates cores in the default processor set. Cores in non-default 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.
Configuring E-Mail on Instant Capacity Systems E-Mail Requirements Previous versions of the Instant Capacity software required e-mail connectivity to HP in order to send asset reports as encrypted e-mail messages. Starting with version B.07.x, Instant Capacity software does not require e-mail connectivity or asset reporting, however, you may choose to configure it because it can be useful for viewing complex-wide asset information at the HP Utility Pricing Solutions portal (http://www.hp.
IMPORTANT: The e-mail is bounced/rejected by the mail servers at HP if the domain name in the FROM address, for the e-mail sent from the Instant Capacity system to HP, is not DNS resolvable by HP. Also, since asset reports are encrypted and must be decrypted at the HP portal, the decryption process may not work correctly if outgoing e-mail sent from your system is automatically modified in any way, for example, to include a privacy notice.
Example A-3 Example Edit to Sendmail Configuration (/etc/mail/sendmail.cf) DMmy_company.com DSmailhub.my_company.com This example assumes the following: • The Instant Capacity system’s hostname is: myICAPsystem.my_site.my_company.com • The From field of the e-mail is set to my_company.com rather than the exact hostname of the Instant Capacity system.
You can verify the configured Instant Capacity FROM e-mail address by using the /usr/sbin/icapstatus command. After you have configured a specified FROM e-mail address, the Instant Capacity software uses it on all subsequent e-mail messages sent from your system. Reverting to the Default FROM Address If you have specified an Instant Capacity FROM e-mail address and you want to revert to the default FROM e-mail address (adm@localhost.
Measurement Software and Instant Capacity Systems Systems with Instant Capacity components (and systems contributing usage rights to Instant Capacity systems) may 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.
Dynamic Processor Resilience (DPR) (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) have been 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.
Security Related Issues Customer protections which iCAP assumes to be in place iCAP commands provide system status information and facilitate system configuration modification, and are therefore executable only by personnel with root level access. An assumption is made that there exist administrative policies which exercise the appropriate degree of control over root level access.
B Considerations for OpenVMS Systems This appendix covers the following topics: • “CLI Support on OpenVMS” (page 194) • “DCL Commands” (page 196) • “Special OpenVMS-Specific Features and Considerations” (page 204) • “Restrictions” (page 205) 193
CLI Support on OpenVMS OpenVMS provides a CLI command interface to the Instant Capacity software. The HP-UX command syntax can be implemented using foreign command symbols. The OpenVMS DCL ICAP command provides DCL command support. 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 three symbol declarations below to your LOGIN.COM file or to the SYLOGIN file to define commands that use the HP-UX syntax.
Table B-1 OpenVMS Command Mapping (continued) HP-UX Style OpenVMS Style icapmanage -s -g [-b] icap manage status [/BRIEF] [/FULL] [-v] icapmanage -R [[,]...] icap manage report [-U ] icapmanage -x icap manage extract OpenVMS iCAP Files The following table lists the files that are new to iCAP version 8.1 on OpenVMS.
DCL ICAP Command The ICAP command supports six command options to perform iCAP operations on OpenVMS systems. DCL Commands ICAP Activate Name ICAP Activate - Immediately activates additional cores on the system. See the HP-UX manpage for icapmodify -a. Format ICAP ACTIVATE /CPU=n [qualifiers] Qualifiers /CPU=n (Required) /Defer /TICAP 196 Specifies the number of additional cores to activate. Defers the activation until the next reboot. See the HP-UX icapmodify manpage for the -D option.
ICAP Apply Name ICAP Apply - Apply an iCAP codeword. See the HP-UX manpage for icapmodify -C. Format ICAP APPLY "codeword" Parameter "codeword" An iCAP codeword obtained from the HP Utility Pricing Solutions portal. The codeword should be enclosed in quotation marks.
ICAP Deactivate Name ICAP Deactivate - Deactivates cores on the system. See the HP-UX manpage for icapmodify -d. Format ICAP DEACTIVATE /CPU=n [qualifiers] Qualifiers /CPU=n (Required) /Defer 198 Specifies the number of cores to deactivate. Defers the deactivation until the next shutdown. See the HP-UX icapmodify manpage for the -D option.
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. See the HP-UX manpage for icapmodify -r.
ICAP Set Name ICAP Set - Sets various iCAP management variables. Format ICAP SET parameter [qualifiers] Parameter Options ACTIVE_CPU Sets the number of active cores and the number of intended active cores. See the HP-UX icapmodify manpage -s option. Format ICAP SET ACTIVE_CPU count Parameter count: the number of cores to set active in the npartition. ASSET Sets the asset reporting e-mail on or off. See the HP-UX icapnotify manpage -a option.
Parameter 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. See the HP-UX icapmodify manpage -w option.
ICAP Show Name ICAP Show - Show the status and settings of the iCAP software on the OpenVMS system. See the HP-UX icapstatus manpage for more information. Format ICAP SHOW STATUS [qualifiers] Parameter status Show the iCAP status and system settings to the standard output device. Qualifiers /SNAPSHOT 202 Creates a string of snapshot information containing encrypted audit data and displays the string to the standard output device. See the HP-UX icapstatus manpage -s option.
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. See the HP-UX icapd manpage for more information. To ensure compliance, the ICAP_SERVER is always running on OpenVMS systems in an iCAP complex.
Special OpenVMS-Specific Features and Considerations Core Activation and Deactivation Unlike HP-UX, the OpenVMS operating system provides a user interface to start and stop system processor resources. When the START /CPU command is used on an OpenVMS system in a complex containing iCAP resources, the ICAP_SERVER validates that the start does not take the complex out of compliance.
Restrictions • • • • OpenVMS 8.3 Instant Capacity software does not support HP virtual partitioning (vPars). Global Instant Capacity (GiCAP) features are not supported, including the use of the icapmanage command. There is no internationalization support, only English language support. LPMC/HPMC are not available on OpenVMS systems.
Glossary 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. active cell A cell that is available for use by the software running on the nPartition. This implies that the cell’s processors and memory (and I/O, if the cell is attached to an I/O chassis) are all available for use by the operating system.
iCOD component See Instant Capacity component. iCOD processor See Instant Capacity core. inactive cell A cell that is not available for use by software running on an nPartition. This term is usually used to describe a cell that has the following status (though any cell that is not active is by definition inactive). • The slot is present and is populated. • Power is enabled. • Boot-is-blocked. • The cell is assigned to an nPartition.
processor The hardware component that plugs into a processor socket. Processors can contain more than one core. Right to Use (RTU) A type of codeword used to activate and adjust available usage rights for Instant Capacity components (memory, cell board, or core). Application of an RTU codeword adjusts the number of component-specific usage rights on the system. system A server, nPartition, virtual partition, or virtual machine that is running an instance of an operating system.
Index activated core defined, 207 activating Cell Board Instant Capacity, 93 activating cores, 59 active cell defined, 207 active nPartition defined, 207 add-on system defined, 207 asset report testing e-mail transmission, 188 assigning cell to partition, 65 assumed values in icapstatus, 170 audit application Instant Capacity, 26 defined, 207 configuring e-mail Instant Capacity, 185 core activated defined, 207 deactivated defined, 207 defined, 207 Instant Capacity defined, 208 core activation Instant Capac
setting system-contact information, 56 TiCAP expiration reminder, 79 undoing incorrect activation, 63 viewing system status, 55 viewing TiCAP usage, 79 exceptions, 122 F failed core replacement, 71 failed monarch processors, 71 failover defined, 207 frequently asked questions Instant Capacity, 130 FROM e-mail address, 187 G Genesis partitions, 177 GiCAP creating groups, 104 group managers, 101 group member reinstallation, 113 member removal, 112 overview, 36, 98 requirements, 100 resource sharing, 107 sha
system hardware, 25 system overview, 24 system status reporting, 44 troubleshooting, 121 troubleshooting software, 125 uninstalling software, 51 upgrading to versions B.06.
S U security related issues, 191 shutting down a partition with Instant Capacity cores, 176 software Instant Capacity, 25 software application considerations, 69 software products Instant Capacity, 24 software requirements Instant Capacity, 30 software validation Instant Capacity, 43 Superdome example of icapstatus on Instant Capacity, 182 supported platforms Instant Capacity, 27, 180 system defined, 209 system contact role requirement, 32 system hardware Instant Capacity, 25 system management commands, 2
