HP-UX HB v13.00 Ch-16 - iCAP

ManualsBrandsHP ManualsSoftwareHP-UX 11i v2 Foundation OE LTU

HP-UX Handbook

Revision 13.00

Chapter 16

Instant Capacity

(iCAP)

Summary of content (24 pages)

PAGE 1
Chapter 16 Instant Capacity (iCAP) HP-UX Handbook Revision 13.
PAGE 2
Chapter 16 Instant Capacity (iCAP) October 29, 2013 TERMS OF USE AND LEGAL RESTRICTIONS FOR THE HP-UX RECOVERY HANDBOOK ATTENTION: PLEASE READ THESE TERMS CAREFULLY BEFORE USING THE HP-UX HANDBOOK. USING THESE MATERIALS INDICATES THAT YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THESE TERMS, DO NOT USE THE HP-UX HANDBOOK. THE HP-UX HANDBOOK HAS BEEN COMPILED FROM THE NOTES OF HP ENGINEERS AND CONTAINS HP CONFIDENTIAL INFORMATION.
PAGE 3
Chapter 16 Instant Capacity (iCAP) October 29, 2013 TABLE OF CONTENTS Introduction ______________________________________________________________________ 4 iCAP Software and Hardware Requirements ____________________________________________ 5 Hardware Requirements ___________________________________________________________________5 Software requirements HP-UX 11.11 _________________________________________________________ 6 Software requirements HP-UX 11.
PAGE 4
Chapter 16 Instant Capacity (iCAP) October 29, 2013 Introduction HP Instant Capacity software provides the ability to instantly increase or decrease computing capacity on specified HP enterprise servers. It is a part of the HP Utility Pricing Solutions program. With Instant Capacity, you initially purchase an HP enterprise server with a specified amount of active processing capacity, and a specified amount of inactive processing capacity.
PAGE 5
Chapter 16      Instant Capacity (iCAP) October 29, 2013 Instant Capacity software Utility Pricing Solutions Portal Instant Capacity Administration System Instant Capacity database Other system management commands Program Requirements To participate in the Instant Capacity version 10.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.
PAGE 6
Chapter 16 Instant Capacity (iCAP) (B9073BA) HP-UX 11i v3 iCAP B.11.31.10.03.00.00 (B9073BA)           rx8640 rx8620 rx7640 rx7620 HP Integrity Superdome 2 Superdome rx8640 rx8620 rx7640 rx7620 October 29, 2013            rp8420 rp8400 rp7420 rp7410 Superdome rp8440 rp8420 rp8400 rp7440 rp7420 rp7410 Software requirements HP-UX 11.11         HP-UX 11i v1 iCAP software bundle B9073BA (version 9.x or later) The kernel configuration must include the diag2 module.
PAGE 7
Chapter 16 Instant Capacity (iCAP) October 29, 2013 Software requirements HP-UX 11.23        HP-UX 11i v2 iCAP software bundle B9073BA (version 10.x) The kernel configuration must include the diag2 module. WBEM B8465BA bundle (version A.02.05 or higher) nParProvider bundle (version B.23.01.06.02 or higher, available from the OE media) If you have a virtual partitioned environment, the Virtual Partitions (vPars) software (bundle T1335BC) must be version A.04.01 or higher.
PAGE 8
Chapter 16 Instant Capacity (iCAP) October 29, 2013 HP OpenView measurement products, such as MeasureWare and GlancePlus, must be version C.02.60 or later to provide correct measurements. Earlier versions of the OpenView measurement products might not work correctly on Instant Capacity systems. Installing/Updating the iCAP Software The following brief overview lists the steps for the installation and configuration of an iCAP system. Consult the official documentation for a full description.
PAGE 9
Chapter 16 Instant Capacity (iCAP) October 29, 2013 1. Execute the icapstatus command: # /usr/sbin/icapstatus 2. Verify that the icapstatus command 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. Log in as root 4. HP recommends that you specify a system contact’s email address on each partition in your system.
PAGE 10
Chapter 16 Instant Capacity (iCAP) October 29, 2013 # /usr/sbin/icapmodify -a <# of cores> [desc[:user_name]]  Deferred until the next reboot by using # /usr/sbin/icapmodify -a <# of cores> -D [desc[:user_name]] 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. If there are no cores with available usage rights: 1.
PAGE 11
Chapter 16 Instant Capacity (iCAP) October 29, 2013 the partition. The exception is the monarch processor as it cannot be deactivated by the LPMC monitor. The failed core is marked for deconfiguration during the next system reboot. If an active core fails with a High Priority Machine Check (HPMC), then upon reboot the failed core is deconfigured and its processing capacity is instantly replaced by an inactive core, if any are available in the partition.
PAGE 12
Chapter 16 Instant Capacity (iCAP) October 29, 2013 2. Install the OS and iCAP software To deactivate the cell board set the cell board’s use-on-next-boot flag to no: # /usr/sbin/parmodify -p -m /::n: Reboot the nPartition, or (on HP-UX 11.31 OEUR 0709 or later) perform a Cell Online Deactivation. This step is not necessary if there was no reboot after the activation.
PAGE 13
Chapter 16 Instant Capacity (iCAP) October 29, 2013 the newly activated core as available for processing. It is recommended to restart the application in this case. Temporary capacity activations are persistent. You need to deactivate cores to stop consumption of temporary capacity. The core deactivation does not need to be on the same partition as the one where they have been activated.
PAGE 14
Chapter 16 have a Instant Capacity (iCAP) machine-readable serial number, as displayed October 29, 2013 by the command: # getconf CS_MACHINE_SERIAL To use GiCAP purchase a special GiCAP Sharing Rights codeword. After purchase, the codeword can be retrieved form the iCAP Portal at http://www.hp.com/go/icap/portal.
PAGE 15
Chapter 16  Instant Capacity (iCAP) October 29, 2013 To view the hardware grouping information, run the command: # icapmanage -R  Now the members need to be added by specifying the name for the new member along with a list of hosts. Specify an OS instance (host) for each nPartition or virtual partition of the complex (do not specify virtual machine or guest OS instances).
PAGE 16
Chapter 16  Instant Capacity (iCAP) October 29, 2013 To remove a member from a group, issue the command # icapmanage -r -m  To remove a group use the command # icapmanage -r -g Group Manager Availability 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.
PAGE 17
Chapter 16 Instant Capacity (iCAP) October 29, 2013 TiCAP for GiCAP systems: 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”.
PAGE 18
Chapter 16 Instant Capacity (iCAP) October 29, 2013 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.
PAGE 19
Chapter 16      Instant Capacity (iCAP) October 29, 2013 Compliance exception Temporary capacity expiration Instant Capacity enforcement Virtual partition boot time compliance Hardware incompatibility in a GiCAP group Starting with iCAP version 8.02, asset reporting is turned off by default for new installations.
PAGE 20
Chapter 16 Instant Capacity (iCAP) October 29, 2013 Troubleshooting iCAP If iCAP does not work properly, the first steps are to verify the software is installed properly and all prerequisites are met:  Verify that the Instant Capacity software is installed and not corrupted: # /usr/sbin/swverify iCOD  Verify that the status of your Instant Capacity system or partition is correct and gather system snapshot information.
PAGE 21
Chapter 16 Instant Capacity (iCAP) HP_iCAPProviderModule HP_GiCAPProviderModule October 29, 2013 OK OK  Make sure partition commands, such as parstatus, are working. For failures in virtual partitions, check the vPar commands such as vparstatus.  Check the iCAP log file and syslog file for any error messages: /var/adm/syslog/syslog.log /var/adm/icap.log /var/adm/icap.log.
PAGE 22
Chapter 16            Instant Capacity (iCAP) October 29, 2013 “Dual-Core Support in Instant Capacity Systems” “New Partition Creation and Instant Capacity” “Implications of Removing a Cell from an Instant Capacity System ” “Shutting Down a Partition with Instant Capacity Cores” “Instant Capacity and Reinitializing the nPartition (Genesis Partitions)” “par Commands from PC System Management Station” “Instant Capacity Compatibility with Processor Sets (HP-UX)” “Configuring Email on Instant Capa
PAGE 23
Chapter 16 Instant Capacity (iCAP) October 29, 2013 iCAP Glossary Actual active cores: This value is listed in the icapstatus output and displays the current number of active cores in the partition. In a virtual partition, the count represents the total number of cores assigned to all virtual partitions. Core: The actual data-processing engine within a processor. A single processor can have multiple cores, and a core can support multiple execution threads.
PAGE 24
Chapter 16 Instant Capacity (iCAP) October 29, 2013 Online activation: The ability to activate a deactivated core while HP-UX is running. No reboot is required. This is done by icapmodify or vparmodify in a virtual partition. Pay per Use (PPU): The HP software product that is a part of the HP Utility Pricing Solutions program. You acquire a specific hardware platform and number of cores and then are charged for usage of the cores based on system demand.