HP Instant Capacity Version 10.x User Guide HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 Abstract This guide provides you with the most recent information for using the Instant Capacity Version 10 software. This document describes Instant Capacity Version B.11.31.10.07.00.00 on HP-UX 11i v3 systems, B.11.23.10.01.00 on HP-UX 11i v2 systems, B.11.11.09.02.00 on HP-UX 11i v1 systems, and Instant Capacity Version 9.x on OpenVMS 8.4 Integrity servers.
© Copyright 2000, 2013 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.
Contents 1 Introduction to Instant Capacity....................................................................9 Instant Capacity summary..........................................................................................................9 Terminology......................................................................................................................10 Overview..............................................................................................................................
Installing from the HP Software Depot (For HP-UX 11i v1, 11i v2, and 11i v3):.............................30 For All HP-UX installations...................................................................................................30 Installing iCAP on OpenVMS systems...................................................................................30 Reinstalling iCAP software.......................................................................................................
Overview..........................................................................................................................59 Ordering iCAP cell board........................................................................................................60 HP-UX and OpenVMS license and support.................................................................................60 Acquiring usage rights for iCAP cell board................................................................................
Deactivating cores.........................................................................................................85 Activating cores............................................................................................................85 Using iCAP memory......................................................................................................86 iCAP use cases..................................................................................................................
Confirming the network requirements:............................................................................108 GiCAP sharing rights for HP Integrity Superdome 2.........................................................108 Creating GiCAP groups...............................................................................................108 Adding members to GiCAP groups................................................................................109 GiCAP resource sharing..............................
Instant Capacity compatibility with Processor Sets (HP-UX)..........................................................188 Overview........................................................................................................................188 Scope of the Instant Capacity software interacting with psets.................................................188 psets on nPars.................................................................................................................189 psets on vPars.
1 Introduction to Instant Capacity This chapter covers the following topics: • “Instant Capacity summary” (page 9) • “Overview” (page 10) For more in-depth information, see icap(5). NOTE: For the latest and most complete information on Instant Capacity refer to Hewlett-Packard's online documentation Web site at: www.hp.com/go/hp-icap-docs Instant Capacity summary HP Instant Capacity software provides the ability to instantly increase or decrease computing capacity on specified HP enterprise servers.
separately. It provides an immediate buffer of temporary capacity in case extra capacity is needed before there is time to purchase an RTU or a TiCAP codeword, or to set up a GiCAP group on an HP-UX system. 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.
Figure 1 (page 11) shows how the iCAP system elements and processes are linked. Figure 1 iCAP system elements System Compliance iCAP DB Codeword Generation Record Purchase iCAP Admin System HP Sales Rep.
• Send configuration change notification, through encrypted email, to the specified system contact. • Monitor and report system compliance (icapd daemon on HP-UX, ICAP_SERVER process on OpenVMS). • Manage GiCAP groups (icapmanage command). For details about these commands on HP-UX, see “iCAP HP-UX Manpages for HP Integrity Superdome 2” (page 124). For the OpenVMS equivalents of these commands, see also “DCL commands” (page 196).
Most recent iCAP product versions and supported platforms Table 1 lists the current versions of iCAP and the platforms supported for each version.
Table 1 Most recent iCAP versions and supported platforms Software and version Operating System version Supported hardware platform — Supported hardware platform — HP Integrity HP 9000 iCAP HP-UX 11i v3 • HP Integrity Superdome 2 • Superdome B.11.31.10.06.01.03 • Superdome • rp8440 (B9073BA • rx8640 • rp8420 Available on: • rx8620 • rp8400 • rx7640 • rp7440 • rx7620 • rp7420 • http://www.hp.com/go/ softwaredepot • rp7410 • HP Integrity Superdome 2 • Superdome B.11.31.10.05.00.
Table 1 Most recent iCAP versions and supported platforms (continued) Software and version Operating System version • http://www.hp.com/go/ softwaredepot Supported hardware platform — Supported hardware platform — HP Integrity HP 9000 • rx7620 • rp7420 • rp7410 • HP Integrity Superdome 2 • Superdome B.11.31.10.00.00 • Superdome • rp8440 (B9073BA) • rx8640 • rp8420 Available on: • rx8620 • rp8400 • rx7640 • rp7440 • rx7620 • rp7420 iCAP HP-UX 11i v3 • http://www.hp.
Past versions and supported operating systems Previous versions of the iCAP software are as follows: 16 • 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.00 (on HP-UX 11i v1 and 11i v2) • B.08.01.
2 Getting Started This chapter covers the following topics: • “iCAP requirements” (page 17) • “iCAP components” (page 21) • “GiCAP” (page 22) • “iCAP codewords” (page 23) • “TiCAP” (page 23) • “iCAP compliance and enforcement” (page 24) • “Configuration change notification” (page 25) • “Core activation” (page 26) • “iCAP cell board” (page 27) • “iCAP software validation” (page 27) • “Status reporting on iCAP systems” (page 28) • “Time zone considerations” (page 28) For more in-depth
HP-UX 11i v1 requirements and dependent products The following software is required for iCAP version 9.x on HP-UX 11i v1: • HP-UX 11i v1 • iCOD software bundle B9073BA (version 9.x) — On the 11i v1 Applications Software media, or download the most recent version from the HP Software Depot at:http://www.hp.com/go/ softwaredepot • The kernel configuration must include the diag2 module. • WBEM B8465BA bundle (version A.02.05 or higher) • nParProvider bundle (version B.12.01.06.
• 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. vPars is available separately and is not included with the OE.
OpenVMS version 8.4 requirements The following software is required for iCAP version 9.x on OpenVMS Version 8.4: • HP OpenVMS Version 8.4 for Integrity Servers or later • iCAP software bundle BA484AA (version 9.x) — Included with OpenVMS Version 8.4 and automatically installed on relevant systems when Version 8.4 is initially installed • WBEMCIM bundle ( version X2.92 or higher) — Optionally installed with OpenVMS Version 8.4 • nParProvider bundle — Installed with OpenVMS Version 8.
Usage rights requirement A system managed under the iCAP program can include one or more components (core, cell, or memory) that are without usage rights. Before you can use these components, you must obtain additional usage rights. Usage rights can either be purchased from HP, or, if the system is a member of a GiCAP group, borrowed temporarily from another member of the group, as described in the section “GiCAP sharing rights” (page 67).
beyond the number of available core usage rights for the complex, but only for a limited period of time. NOTE: Unless a system participates in a GiCAP group (see Chapter 7), usage rights are complexwide (single node for OpenVMS) only. If components are moved from one complex to another, the counts of allowable active and inactive components do not change for either complex. In particular, the number of “expected inactive” components of each type does not change if components are removed.
to the Group Manager system enables the addition of members with iCAP components to groups. In addition, you must acquire grouping rules from the portal and apply those rules to the Group Manager system. GiCAP sharing rights and grouping rules are described in Chapter 7 (page 64). All GiCAP Group Manager systems and group members must run iCAP version 9.0 or later.
NOTE: TiCAP cannot be used to activate inactive iCAP cell boards or memory. To activate cores on an inactive cell board, you must first activate the cell board and its memory either by using newly purchased cell and memory usage rights or by deactivating a cell board and memory elsewhere in the server. Your temporary capacity balance is decreased only when you are using more cores than normally allowed by your available core usage rights.
The enforcement methods used by the software include: • Not allowing activations that cause the system to be out of compliance • Deactivating cores at power-on (boot) time: ◦ Automatically deactivate cores at power-on (boot) time if temporary capacity is exceeded and the number of active cores continues to exceed the number of core usage rights for the complex (see “TiCAP expiration and compliance enforcement” (page 55)).
Example 1 Configuration Change Notification email for iCAP System (not vPar) Subject: Instant Capacity Configuration Change Notification A configuration change has been made to the following system: super.corp.com One or more cores were activated.
IMPORTANT: To avoid a delay in activation of additional cores, purchase and keep in reserve some quantity of temporary capacity for the system. Temporary capacity can be used to instantly and temporarily activate cores while waiting for an RTU codeword. For details about temporary capacity, see Chapter 5. You can also temporarily activate one or more cores using the Instant Access Capacity (IAC) provided with the purchase of iCAP processors.
iCAP software separately on OpenVMS systems. Onsite iCAP installation by an HP service representative after the initial installation of OpenVMS Version 8.3 is not an option for OpenVMS systems. To verify that the iCAP software is installed and configured, run the following commands: $ @sys$manager:ICAP$CLI_UTILS.COM CONFIG_CHECK $ show log ICAP$CONFIGURED "ICAP$CONFIGURED" = "TRUE" (LNM$JOB_nnnnnnnn) Status reporting on iCAP systems You can use the icapstatus command to view the status of your iCAP system.
3 Installing and removing iCAP software This chapter covers the following topics: • “Installing iCAP software” (page 29) • “Reinstalling iCAP software” (page 31) • “Removing iCAP software” (page 31) Installing iCAP software Factory Integrated Systems The iCAP software is installed by HP on all HP enterprise servers, even those without iCAP components.
2. Determine the DVD drive device file by entering the following command: ioscan -fnC disk 3. 4. Insert the appropriate HP-UX Applications Software or OE DVD into the DVD drive. Mount the DVD drive to the desired directory. The following example uses the /dev/dsk/ c1t2d0 device file (from step 2) and the /dvd directory. To mount the DVD drive, enter a similar command as: mount -r /dev/dsk/c1t2d0 /dvd 5. Install the B.10.x bundle B9073BA from the DVD: swinstall -s /dvd B9073BA 6.
$ @sys$manager:ICAP$CLI_UTILS.COM CONFIG_CHECK $ show log ICAP$CONFIGURED "ICAP$CONFIGURED" = "TRUE" (LNM$JOB_nnnnnnnn) Reinstalling iCAP software Preserving current iCAP information If you reinstall HP-UX on a partition with iCAP (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 iCAP configuration file (change history, system contact information) is lost.
4 Using iCAP to manage processing capacity This chapter covers the following topics: • “Checking the status of your iCAP system” (page 32) • “Setting system contact information” (page 34) • “Applying a Right To Use (RTU) codeword” (page 35) • “Activating Cores” (page 36) • “Deactivating cores” (page 38) • “Overriding deferred activation and deactivation” (page 39) • “Load-balancing active cores” (page 40) • “Understanding and managing intended active values” (page 41) • “Activations and dea
• • • Local nPartition status (if not a virtual partition): ◦ Date and time the command was issued ◦ Total number of configured cores ◦ Number of intended active cores ◦ Number of active cores ◦ Number of inactive cores ◦ Additional cores that can be activated with current usage rights ◦ Number of cores that could be activated with additional usage rights ◦ Number of cores that can be activated with temporary capacity ◦ Number of cores that are deconfigured or attached to inactive cells
Example 2 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.71 supericod 1234567890 A6912A fffff-fff-ffffff-ffff mjones@corp.
NOTE: iCAP email messages are sent to the system contact email address, if specified, and the root account on the partition. Most notifications are also written to the system log. To specify the iCAP system contact’s email address, use the icapmodify -c command. Note that you must specify a valid Internet email address. For example: > /usr/sbin/icapmodify -c mjones@corp.com The contact email address has been set to mjones@corp.com.
Figure 2 Permanent activation of iCAP 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 Send Ack Letter Post IAC in iCAP DB Process Order for RTU(s) Post RTU Order in iCAP DB Activating Cor
IMPORTANT: If you shut down a partition for 12 hours or more, it should be powered off or deactivated to avoid additional charges. To power off the partition, execute the PE command from the system MP. On HP-UX systems, always use the shutdown -R -H command when shutting down or rebooting an iCAP partition. If the partition is already shut down, use the rr command from the system MP to reset cells for reconfiguring. For information about the shutdown command, see shutdown(1M).
NOTE: To defer the activation until the next reboot, add the -D option to the command. For more information, see icapmodify(1M). The icapmodify command allows you to activate additional cores with the -a option, or set the total number of active cores with the -s option. For example, the icapmodify -a 2 command activates two additional cores in a partition. The icapmodify -s 2 command sets the total number of active cores in a partition to 2.
Example 5 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 5, 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.
Example 6 Correcting an incorrect number of deferred active cores (HP-UX) 1. On your system or partition you currently have 2 active cores and 2 inactive cores. You need 4 active cores, so you perform a deferred activation for 2 additional active cores by entering the following command: /usr/sbin/icapmodify -D -a 2 2. Later, and prior to a system reboot, you realize that you need only 3 active cores (not 4).
redistribution, it remains in compliance. Make sure that you have proper licensing for all proprietary and nonproprietary software when performing load balancing. Understanding and managing intended active values The iCAP 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.
NOTE: Deferred activations and deactivations are not supported in any virtual partition environment. iCAP always consumes unused capacity before it consumes additional usage rights when activating cores. iCAP always releases usage rights from unused capacity before it releases usage rights by deactivating cores. When to use the vparmodify or icapmodify commands When usage rights freed by deactivating cores are to be used in a different nPartition, use the icapmodify command.
efficient way to adjust capacity within virtual partitions of a single nPartition, but it does not affect the intended active count for the nPartition. Therefore, it cannot be used to migrate unused capacity either to or from other nPartitions. When you execute the vparmodify command to activate a core, the command verifies with the iCAP software how many cores are available for activation.
Example 8 vPar Boot–Time compliance message To: root@par1.yourorg.com Subject: vPar Boot Time Compliance This message is being sent to inform you that a vpar is not being allowed to boot because doing so would take this complex out of compliance from an Instant Capacity perspective. The number of cores assigned to this vPar database (/stand/vpdb) exceeds the number of intended active cores by 1.
icapstatus value for Additional cores that can be activated with current usage rights or the actual number of cores, whichever is smaller. To assign an inactive cell to a partition, this value must be nonzero.) However, when a new partition is created via the parcreate command, core usage rights must be available for all cores configured on the new partition's cells, and core usage rights are automatically assigned to these new cells.
Figure 9 Partition premodification state: Three cells with 3 active and 1 inactive cores in each, and 3 expected inactive cores Cell 1 A A Cell 2 A A I A Cell 3 A A I A A I Figure 10 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 11 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 una
is required for activation of a core without usage rights for testing purposes. For details, see Chapter 5: “TiCAP” (page 49). The following testing guidelines are meant to be an aid to your test plan. You might need to get consulting help to develop a more detailed plan. 1. Test your applications for proper functionality and performance first by testing with the number of inactive cores equal to the number of cores without usage rights. (The system should already be configured this way.
If your system has only one active processor, that processor is considered a monarch processor and it cannot be replaced on line. A reboot of the system is required to replace the failing monarch processor. If there are multiple active processors in your system, one of them is designated as the monarch processor, and the other (nonmonarch) processors can be replaced on line. If the monarch processor fails, it cannot be replaced without a reboot.
5 TiCAP This chapter covers the following topics: • “TiCAP overview” (page 49) • “Ordering TiCAP” (page 50) • “Using TiCAP” (page 51) • “TiCAP and vPars” (page 52) • “Tracking usage of TiCAP” (page 53) • “TiCAP warning period” (page 54) • “TiCAP expiration and compliance enforcement” (page 55) • “TiCAP exceptions” (page 55) TiCAP overview You can purchase an amount of temporary capacity (TiCAP) time for inactive cores without usage rights in your iCAP system.
Figure 12 Using TiCAP: 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 Ordering TiCAP To add temporary capaci
OpenVMS licensing and support with TiCAP When you purchase temporary capacity, the temporary OpenVMS license-to-use is included when iCAP cores are activated using temporary capacity. The OpenVMS License Management Facility recognizes when TiCAP cores are activated, and they treat the usage as compliant. For nonproprietary software that uses per-core licensing, check with the vendor for licensing requirements.
Example 10 Activating an iCAP Core with TiCAP (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 iCAP cores in inactive iCAP cell boards. You must purchase additional usage rights for the cell board and perhaps also for the memory of the cell board.
Instant Capacity Resource Summary --------------------------------Number of cells without usage rights: 0 Number of inactive cells: 0 Amount of memory without usage rights: 0.0 GB Amount of inactive memory: 0.
TiCAP Expiration Reminder The iCAP software calculates when the temporary capacity balance will expire, based on the current consumption rate. After the temporary capacity balance reaches a certain residual number of days (see “TiCAP warning period” (page 54)), a reminder email message is automatically sent to the system contact, if one is specified, and root. These messages are sent on a daily basis until temporary capacity expires. Example 12 shows a temporary capacity expiration reminder email message.
TiCAP 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.
icapstatus output). When this state occurs, you need to take corrective action immediately by doing one of the following: • Deactivate iCAP cores that are using temporary capacity. • Apply additional temporary capacity codewords. • Acquire additional core usage rights and apply the RTU codeword. Temporary capacity negative balance A complex is out of compliance with the iCAP contract if a negative balance of temporary capacity occurs.
Example 14 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 15 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 iCAP cell board This chapter covers the following topics: • “iCAP cell board” (page 59) • “Ordering iCAP cell board” (page 60) • “HP-UX and OpenVMS license and support” (page 60) • “Acquiring usage rights for iCAP cell board” (page 60) • “iCAP cell board and considerations of core usage rights” (page 61) • “Activation of an iCAP cell board” (page 62) • “Accidental activation of an iCAP cell board” (page 62) • “iCAP cell board activation exception error” (page 63) • “iCAP cell board and Ti
After a cell board is activated, all of the cores on the cell board can be activated, depending on the availability of core usage rights. You might need to acquire additional core usage rights to activate additional cores from the newly activated cell board. For information about assigning and unassigning a cell board to an nPartition, see “Assigning a cell to a partition” (page 44) and “Unassigning a cell from a partition” (page 45).
HP sends you a letter that tells you on how to acquire RTU codewords for the purchased components. The letter also describes how to apply the codewords to the system to increase the usage rights on the complex. The steps are as follows: 1. Acquire the appropriate RTU codeword (cell board, memory, core) from the Utility Pricing Solutions portal (http://www.hp.com/go/icap/portal). 2. Apply the appropriate RTU codeword (cell board, memory, core) using the icapmodify -C command.
requires purchase of an additional core usage right to meet the minimum requirement of 1 core per active cell board. Table 3 Cell board activation requiring additional core usage rights State Active Cell Board Cores Inactive Cell Board Cores Notes Before Cell Board Activation 1 active, 3 inactive 4 inactive No core usage rights are available on the complex.
iCAP cell board activation exception error When you attempt to activate an iCAP 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 13, Figure 14, and Figure 15 illustrate this.
7 GiCAP This chapter covers the following topics: • “GiCAP overview” (page 64) • “GiCAP requirements” (page 65) • “GiCAP Group Managers” (page 66) • “GiCAP grouping rules” (page 67) • “GiCAP sharing rights” (page 67) • “GiCAP Group creation” (page 68) • “GiCAP resource sharing” (page 70) • “GiCAP and temporary capacity” (page 73) • “Removing a GiCAP group member” (page 74) • “Reinstalling a group member” (page 74) • “Group Manager availability (no standby manager)” (page 75) • “Group
Manager. Applying this codeword on a system running iCAP enables the creation of a GiCAP group with members. Figure 16illustrates the process of configuring and using GiCAP.
GiCAP 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 iCAP software version 9.0 or later. The system running the Group Manager does not require any iCAP components, and it does not need to be a partitionable system.
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.
information, if any. Use the icapmanage -s command on the Group Manager system to retrieve the serial number and nPar ID, or vPar code that is applicable. GiCAP codewords 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.
group. Deactivating resources on these systems allows them to loan usage rights to other members in the group. Example 17 shows how to create a group and show group status. Example 17 Creating a group > icapmanage -a -g one Group one added. > icapmanage -s Software version: B.09.
Example 19 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.
• 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. • Even if there are no unused usage rights across the group, a member of the group can deactivate resources (cores, cells, or memory) to make additional usage rights available for activation by any other member in the group.
Whenever you have more active cores than the number of core usage rights, the temporary capacity balance is depleted as a mechanism for tracking noncompliance of the group, even if TiCAP has not been purchased for or applied to any member of the group. This differs from the behavior of TiCAP on a complex which is not a member of a group, where TiCAP is decremented only if TiCAP had been specifically purchased for the complex.
Amount of inactive memory: Number of cores without usage rights: Number of inactive cores: 16.0 GB 8 8 The output of the icapstatus command on member2 shows that memory and cell usage rights are available, along with 1 core usage right: Instant Capacity Resource Summary --------------------------------Number of cells without usage rights: Number of inactive cells: Amount of memory without usage rights: Amount of inactive memory: Number of cores without usage rights: Number of inactive cores: 1 2 16.
output is updated on both systems to reflect the transfer. Because of the delay, the changes might appear to be unrelated to a user-initiated operation, but they are due to the previously initiated deactivation that freed up core usage rights. Temporary capacity and status reporting The temporary capacity balance reported by icapstatus on a group member reflects only the temporary capacity that has been applied or transferred to that system via the Group Manager.
See the HP Instant Capacity Release Notes for more details about reestablishing SSL certificates. 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.
Upgrades and GiCAP 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.
do not expire. The icapmanage -z command allows you to restore previously seized core usage rights to a specified host. The following command seizes core usage rights from a partition that is unavailable, so that the rights are available for other group member activations: icapmanage -x mypar1.node.corp.
rights are available to other group members for purposes of disaster recovery. If none of the member partitions are reachable by the expiration date for a particular member, the usage rights are automatically restored (reassigned) to the member partition (or complex, in the case of unassigned seized rights) from which they were seized.
Additional HA solutions Although rights seizure is the main method used in a GiCAP high availability (HA) scenario, there are additional methods and configurations allowing GiCAP to provide you with HA solutions: • You can use GiCAP to move capacity from one or more nonproduction servers, such as test servers, during a failover situation. You have a set of standby servers that are part of a group and can pool their resources to provide failover capability. • You can combine GiCAP with temporary capacity.
In either of these cases, rights seizure is the only technique available for migrating core usage rights from the nPartition. • Because rights are seized at the nPartition level, when an entire server is unavailable, to seize all rights from the server, the icapmanage -x command must be run for each nPartition in the server. • An nPartition must be unavailable for usage rights to be seized. Usage rights can be seized only if the partition is unavailable as determined by the ping command.
Sharing rights can never be applied to a Group Manager with standby status. If a standby Group Manager is requested to take control, the sharing rights of the former active Group Manager move to it. If additional sharing rights need to be applied before failing back to the original Group Manager, they must be purchased specifically for the new active Group Manager system (formerly the standby Group Manager) and acquired from the portal.
8 Using iCAP on HP Integrity Superdome 2 This chapter discusses iCAP features on HP Integrity Superdome 2 systems. Depending on the Onboard Administrator (OA) firmware version, the functionalities of HP Integrity Superdome 2 systems might differ. For information on the iCAP features on HP Integrity Superdome 2 with dynamic cores capabilities, see “HP Integrity Superdome 2 with Dynamic Cores” (page 92).
2. Sign in to the portal using your Passport ID. If you are a first time user, you must register on this portal to obtain a Passport ID. 3. Click Create codewords. NOTE: For self enforcement, codewords are not provided but the process used for inventory tracking mirrors what is used for codewords. 4. 5. Follow the prompts as if you were going to generate a GiCAP code word. Subscribe to receive a mail or keep a record of the transaction.
inactive memory on an iCAP cell blade has to be activated at the same time. Until the memory is activated, the iCAP cell blade is considered to be logically powered off. To comply with the iCAP Terms & Conditions, HP recommends you to power off the iCAP cell blade that contains iCAP memory. After purchasing enough memory RTUs to activate all of the iCAP memory on the cell blade, update the iCAP inventory on the HP Utility Pricing Portal.
Number of Temporary Projected Temporary cores using temporary capacity: 0 capacity available: 5 days, 18 hours, 28 minutes(8308 minutes TiCAP ) temporary capacity expiration: N/A capacity warning period: 15 days Generating snapshot An audit snapshot is to be presented at the Utility Pricing Portal while purchasing usage rights for iCAP resources. The audit snapshot is an encrypted representation of the iCAP resources on the complex.
activating them. that is, core activation request will fail if the request exceeds the assigned number of cores for the partition. Execute the following command to activate the cores: icapmodify –a Sample output: # icapmodify -a 1 4 cores are intended to be active and are currently active. Using iCAP memory The iCAP memory is offered in units of 16 GB, and the RTU is available in units of 4 GB.
Table 4 Use case 1 — Initial configuration Partition Total Cores Total Active Cores nPar1 16 12 nPar2 8 2 Core migration from nPar1 to nPar2 can be done as follows: In nPar1: # icapmodify –d 2 10 cores are intended to be active and are currently active. In nPar2: # icapmodify –a 2 4 cores are intended to be active and are currently active. IMPORTANT: To remain in compliance, you must perform the deactivation operation first. Core migration between the partitions is now complete.
# icapmodify –d 3 5 cores are intended to be active and are currently active. The usage rights obtained from complex2 can be distributed among the partition(s) of complex1. In this use case, we distribute it among nPar1 and nPar2. In nPar1: # icapmodify –a 2 14 cores are intended to be active and are currently active. In nPar2: # icapmodify –a 1 11 cores are intended to be active and are currently active. Core migration between the complexes is complete.
Temporary capacity available: 2 days, 5 hours, 20 minutes(3200 minutes TiCAP) This assigns 3200 minutes of TiCAP to the partition npar2. IMPORTANT: Self-enforcement requires that the sum of the TiCAP assigned to the partitions in a complex must not exceed the TiCAP bought for the complex.
The consumption of temporary capacity can be stopped by deactivating cores that are using temporary capacity using the following command: icapmodify –d Sample Output: #icapmodify -d 2 11 cores are intended to be active and are currently active.
Npar2 300 minutes Migrating TiCAP balance between complexes (within GiCAP) Consider 2 complexes , complex1 and complex2 with the following configuration: Complex 1: Partitions TiCAP Balance Npar1 500 minutes Npar2 500 minutes Complex 2: Partitions TiCAP Balance Npar3 100 minutes Npar4 100 minutes TiCAP Balance migration from complex 1 to complex 2 can be done as follows: 1. Select partition(s) in complex 1 to decrement the TiCAP Balance. Here we select npar1. 2.
HP Integrity Superdome 2 with Dynamic Cores Overview The iCAP software on the HP Integrity Superdome 2 complex with dynamic cores capability, performs a compliance check on the complex, to check if the complex meets the iCAP contract. Usage rights are managed through the application of codewords. The codewords, wherever applicable, must be obtained from the iCAP portal and applied on the system. The usage rights (including temporary capacity) are managed at the complex level.
6. Modify the count of cores for partitions so that they boot up with the expected number of cores. Expected number of cores must match the number of cores that were active for each partition in Step 2.
NOTE: For detail information on how to migrate self enforcement system to codeword managed system, see the whitepaper in the Upgrading to HP Instant Capacity with dynamic cores on HP Integrity Superdome 2 servers (http://h20195.www2.hp.com/v2/GetPDF.aspx/ 4AA3-7036ENW.pdf).
Applying a Right To Use (RTU) codeword Unless you have a balance of IAC or temporary capacity (or usage rights available from a GiCAP group), you must purchase additional usage rights before the activation of an inactive core. To purchase additional usage rights: 1. Contact your HP sales representative to purchase the appropriate iCAP RTU products. 2. Acquire an RTU codeword from the Utility Pricing Solutions web portal at: http://www.hp.com/go/icap/portal 3.
Warning period for core temporary capacity expiration : 0 Days 0 Hours Number of cores using temporary capacity : 0 Memory Usage Right Details -------------------------Total memory usage rights (in GB): 78.0 Committed memory usage rights (in GB) : 78.0 Available memory usage rights (in GB) : 0.
# icapmodify -d 1 6 core units are now active NOTE: If the core deactivation command is run on the Onboard Administrator, the partition ID must be specified using the p option as follows: icapmodify -d -p Deactivating Cores in nPartitions The software provides two types of core deactivation: • Instant (the default behavior for the icapmodify command) — deactivation occurs immediately. • Deferred (icapmodify -D) — deactivation occurs after the next reboot of the partition.
contains enough unassigned 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).
Authorizing TiCAP To utilize the available temporary capacity to activate cores in the absence of usage rights, you can use the icapmodify with the -t option along with either the -a or the -s option. When the -s option is specified, the number of cores entered must be greater than the current active cores in the partition.
Table 10 TiCAP Preauthorization usage matrix (continued) TiCAP Partition Preauthorisation Type flag -T (on/off) Operation nPAR Reboot nPAR vPAR vPAR ON OFF ON OFF Reboot Power-on/boot Power-on/boot 100 Using iCAP on HP Integrity Superdome 2 When to use it? Example: Partition state before Comments operation If sufficient RTUs are not available to boot nPAR with IA cores and user want to reboot nPAR using TiCAP balance. nPAR will boot up using RTUs only or using both TiCAP balance and RTUs.
Table 10 TiCAP Preauthorization usage matrix (continued) TiCAP Partition Preauthorisation Type flag -T (on/off) Operation When to use it? user do not want to boot using TiCAP. vPAR vPAR ON OFF Reboot Reboot If sufficient RTUs for the cores assigned to a vpar are not available and user want to use TiCAP to reboot a vpar. If sufficient RTUs for the core assigned to a vPAR are available. Example: Partition state before Comments operation Partition state after operation completed all.
To deactivate one or more cores in a partition from the Onboard Administrator, use the following: icapmodify -d -p par_id Setting the temporary capacity warning period By setting the warning period to ‘x’ days, you can receive mail notifications if the partition’s temporary capacity is projected to expire within the next ‘x’ days. Appropriate actions can then be taken to replenish the temporary capacity balance.
Example 20 Temporary capacity information from icapstatus command (HP-UX) Summary of iCAP contract -----------------------State of iCAP contract : compliant Complex TiCAP pre-authorization is turned off System contact email id : mjones@corp.
Example 21 Error message for activation with insufficient TiCAP (HP-UX) > icapmodify -t -a 2 iCAP authorization denied for partition 2. Error: Insufficient usage rights or temporary capacity for 2 additional cores. TiCAP negative balance A complex is out of compliance with the iCAP contract if a negative balance of temporary capacity occurs. The iCAP software sends you an exception report (via email) if there is a negative balance of temporary capacity.
Example 22 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 23 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.
NOTE: Communication between the managers and members of groups is established using the SSL certificates that are supplied by the GiCAP software and the Onboard Administrator. To create a GiCAP group with members, you must: 1. Purchase new GiCAP sharing rights for the HP Integrity Superdome 2 systems. 2. Acquire the GiCAP codeword from the HP Utility Pricing Solutions portal. 3. Apply the GiCAP codeword to the Group Manager system. 4.
NOTE: • The options I and P will work only from AGM. • icapmanage command does not check if the given IP address is correct or not. It is users responsibility to provide a correct IP address of AGM or SGM. • icapstatus on members will show IP address of AGM or SGM instead of the names. • The active_gm and standby_gm users must not already exist on the Onboard Administrator.
Adding members to GiCAP groups After the GiCAP group is created, you can use the following command to add the HP Integrity Superdome 2 systems to the group: icapmanage -a -m : -g You can specify the host name of both the Active Onboard Administrator and Standby Onboard Administrator to improve the high availability: icapmanage -a -m :, , -g group_name In this case, the ENCLOSURE_IP_MODE value needs to be disabled on
Removing an HP Integrity Superdome 2 system with negative temporary capacity balance is not allowed. User cannot remove this member while it is out of compliance. User needs to transfer some amount of temporary capacity from other group member(s) by using temporary capacity and stopping it. User can also purchase additional temporary capacity. When the member is in a compliant state, you can remove the member from the group.
Removing a standby Group Manager To remove the standby Group Manager assigned to the groups, issue the following command on the active Group Manager: icapmanage -r -S The following example shows how to remove a standby Group Manager: # icapmanage -r -S standyhost.yourdomain.com Host standyhost.yourdomain.com has been removed from use as a standby Group Manager.
9 Troubleshooting This chapter covers the following topics: • “Handling compliance exceptions” (page 112) • “Troubleshooting the iCAP software” (page 114) • “Diagnosing email configuration” (page 116) Handling compliance exceptions A complex can get out of compliance with the iCAP 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).
Example 24 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.
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.
If there is a discrepancy between the number of reported components with or without usage rights and your iCAP contract, contact your local HP Response Center and request iCAP assistance. 4. Ensure that the required processes for iCAP are running. On HP-UX systems, verify that the icapd daemon is running on the system or partition by entering the following command: /usr/bin/ps -e | grep icapd The command indicates that the icapd daemon is running on the partition.
9. View the iCAP log file and syslog file for any error messages. On HP-UX systems, these files are /var/adm/icap.log and /var/adm/syslog/syslog.log. On OpenVMS systems, these files are sys$manager:icap.log and sys$manager:operator.log. Additional Troubleshooting Steps for Email Connectivity If you are using asset reporting, perform the following additional troubleshooting steps to make sure that HP is able to receive an email message from the iCAP software: 1.
2. 3. Look for the certificate which contains the Common Name mentioned in the OA certificate on the member. OA certificate information can be obtained on the member, by executing Show OA certificate on the OA cli. Then execute the cimtrust -r i -S command to remove the certificate. Issuer and subject information should be taken from cimtrust -l output.
10 Frequently asked questions This chapter covers frequently asked questions on the following topics: • “iCAP software” (page 118) • “iCAP hardware” (page 121) • “GiCAP” (page 121) iCAP software What software product is required for iCAP on Itanium-based servers running HP-UX? The HP software bundle for the iCAP version 10.x software, on Itanium-based servers running HP-UX 11i v2, or 11i v3, is HP product number B9073BA.
• A partition with iCAP has a configuration change (that is, a core is activated or deactivated). • A codeword is applied. • Usage rights are seized from a GiCAP system. You can view all events in the iCAP log files in the /var/adm/icap.log or /var/adm/ icap.log.old file on HP-UX systems, and in the sys$manager:icap.log file on OpenVMS systems. GiCAP events can be viewed on the Group Manager system in /var/adm/GiCAP.log (see “GiCAP” (page 121)).
Table 11 Email sent by the iCAP software (continued) Triggered By Email Message icapd (daily, if more than expected cores, memory, cells, are active; also if TiCAP has a negative balance) An exception report (for noncompliance) is sent to the system contact, if specified, and root. icapd (if one or more cores are deactivated at boot time to enforce compliance) An iCAP enforcement message is sent to the system contact, if specified, and root.
iCAP hardware Can a faulty cell board be replaced with an inactive iCAP 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. GiCAP 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.
11 Support and other resources New and changed information in this edition To review what is new and changed in this release of HP iCAP, see the HP Instant Capacity Version 10.x Release Notes at www.hp.com/go/hp-icap-docs. Typographic conventions This document uses the following conventions: %, $, or # 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. audit(5) A manpage.
Location of iCAP information iCAP version 10.x user guide You can find the HP Instant Capacity Version 10.x user guide in the following locations: • www.hp.com/go/hp-icap-docs These are the most current and the most current localized versions of the user guide. • March 2012 HP-UX 11i v3 Instant Information media (English, Simplified Chinese, and Japanese only) • In the iCAP 10.x HP-UX software product: /usr/share/doc/icapRelNotes.pdf • On the OpenVMS Version 8.
iCAP HP-UX Manpages for HP Integrity Superdome 2 124 iCAP HP-UX Manpages for HP Integrity Superdome 2
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.
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 are generated. After the appropriate codewords are applied to a complex, additional components in the complex may be activated, up to a maximum number of component usage rights granted by the applied codewords.
Instant Capacity can be present on 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).
extra capacity is needed before you purchase either an RTU codeword, a temporary capacity codeword, or setup a GiCAPgroup. TiCAP can be added to the complex by applying a temporary capacity codeword (available from the HP Utility Pricing Solutions portal) using the icapmodify command. Information about the amount of temporary capacity time remaining on a complex can be obtained by executing the icapstatus command.
components, nor does it need to be a partitionable system. The system must have a machine-readable serial number, as displayed by the shell command getconf CS_MACHINE_SERIAL. HP recommends that the Group Manager must not be on a partition that is a member of any GiCAP group, and that it manages a single group. If run on a partitionable system, changing the configuration of the partitions may result in the GiCAP Manager becoming inoperative.
Each member that joins the group decreases the available GiCAP sharing rights by the number of cores without usage rights contributed by that member complex. GiCAP resource sharing After 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. Usage rights are shared by deactivating resources on one group member, and then activating resources on another member of the group.
had been specifically purchased for the complex. Within a GiCAP group, temporary capacity is used as an additional compliance mechanism to support the high availability features of a group.
critical group members. When a standby manager takes control, it attempts to update all members and the current active Group Manager so that group operations can proceed smoothly. However, in the case of a failure, it is possible that the icapmanage -Q command is unable to contact the active Group Manager and some members of the groups that it now manages. When this happens, the previously active Group Manager remains active, unaware of the change of control.
SEE ALSO icapmodify(1M), icapnotify(1M), icapstatus(1M), icapmanage(1M), icapd(1M), parmgr(1M), parmodify(1M), parolrad(1M), vparmodify(1M).
icapmanage(1M) NAME icapmanage -- GiCAP management commands for GiCAP groups.
are allowed, all other options are restricted to use only on the active Group Manager. The icapmanage command should not be invoked on a group member system.
-h Used with the -u option 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 an exclamation point (!) 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. -i Install a grouping rules file on a Group Manager system.
Removal of a member from a group releases sharing rights and makes them available for future use. When used in combination with the -g option, removes the specified GiCAP group. All members must be removed before the group can be removed. When used in combination with the -S option, removes the identified host system from use as a standby Group Manager. -s Request status about one or more GiCAP groups.
When adding hosts, each host must be up and the Group Manager must be able to contact it. (To avoid potential problems, the Group Manager should also be able to contact any standby manager that is defined.) NOTE: -v option "-u" is not supported on Sd2 systems. 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.
At the time of rights seizure, if at least one member partition can be contacted, the software is able to make an immediate adjustment to the available core usage rights, as if an icapmodify -d operation had been performed before the specified hard partition stopped running. This makes core usage rights available for potential loans to other member systems. In this situation, the seized core usage rights do not have an expiration date.
operation or as the target of a usage rights restore operation. • -z Because rights seizure leaves only a minimum of core usage rights with the nPartition, it is likely that the remaining number of core usage rights is not sufficient to satisfy the number of cores assigned to each virtual partition in the nPartition. This means that the virtual partitions cannot be booted (due to noncompliance) after the original failure is corrected.
regardless of whether these attempted contacts succeed or fail. When attempting to contact all group members, the new active Group Manager may find that it must establish SSL communication with a member host. If so, it prompts for that host's root password so that it can exchange SSL keys with the host (unless the -n option is also specified). HP recommends that SSL communication between the standby Group Manager and all member hosts is established before the use of the icapmanage -Q command.
Group Manager. The active Group Manager updates all member hosts of all managed groups about the removal, discontinues the GiCAP database transfer operations (removes the cron job created when the standby Group Manager was set up), and directs the identified host system to remove its copy of the GiCAP database.
# Indicates that all cores in the partition, rather than any specific number, have been requested to be active. The number indicates the current number of cores in the partition. Information displayed for each GiCAP group These values can be displayed for each group managed by the Group Manager. Group : Displays the name of the GiCAP group. Group Members: Summarizes the name of each member in the group, and also shows the host names comprising each member complex.
usage rights that are not in use. It is displayed only when the -v option is specified. Unassigned memory usage rights: Displays the amount of memory that can be activated immediately in the group because of usage rights that are not in use. It is displayed only when the -v option is specified. Unassigned core usage Displays the number of cores that can be rights: activated immediately in the group because of the usage rights that are not in use. It is displayed only when the -v option is specified.
the overall balance of cores without usage rights that must be maintained in the group. If none of the partitions of the member can be contacted, then the Resource Summary contains limited information, using the last-known values for the member. Only the fields listed for unreachable members have values that are included in the group totals.
reconnection, the seized usage rights revert to the member system from which they were seized. Core usage rights seized from npar : Displays the number of expiring core usage rights that were seized from a specific partition of the member. It is displayed only when the -v option is specified, and it is repeated for each partition where usage rights are seized for disaster recovery, if none of the member partitions could be contacted.
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. • LC_MESSAGES determines the language in which messages are displayed.
icapmanage -a -g ADMIN1 Test whether a server complex has hardware that is compatible with the group: icapmanage -T mypar1.node.hp.com,mypar2.node.hp.com -g ADMIN1 Add a member called IT to the ADMIN1 group. Supply the root password for each of these partitions in response to the prompts: icapmanage -a -m IT:mypar1.node.hp.com,mypar2.node.hp.com -g ADMIN1 root@mypar1.node.hp.com’s password: root@mypar2.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 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.
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. If unused capacity is available, icapmodify will first activate cores from unused capacity before increasing the active cores.
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. • LC_TIME determines the date and time strings output. • LC_MESSAGES determines the language in which messages are displayed.
icapmodify -C 7y5ejVS.P5CuwXu.XaTyDVP.7Tx0Mvc-J783H9b.yWT5Weu.69JPu$u.vVV685a5 Set the Instant Capacity from_email_address to admin@research.corp.com: 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: 0 Command succeeded. >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.
From email: 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. Asset reporting: Indicates if the Instant Capacity software on the local system is presently configured to send email asset reports to HP. This is configured using the icapnotify -a command.
command on the Group Manager system to get more complete information about available group resources. When a group member is using temporary capacity and core usage rights are made available on another group member through the use of icapmodify -d , there may be a delay between the time the core usage rights are made available and the time the core usage rights move to the group member using temporary capacity.
Information displayed for the local nPartition In addition to displaying the current date and time as part of the heading, the following status is displayed when icapstatus is run on a hard partition. Much of this information is also displayed when icapstatus is run on a virtual partition, except as otherwise specified. Note that some of the displayed information pertains specifically and only to the local hard partition (such as the “number of active cores” or “number of inactive cores”).
Instant Capacity resource summary The following status is displayed for the entire complex: Number of cells without usage rights: Displays the number of configured cells in excess of the number of cell usage rights applied to the complex (purchased rights or borrowed from a GiCAP group). Therefore, this number represents the count of cells which are expected to be inactive. Number of inactive cells: Displays the current number of inactive cells in the complex.
Actual active cores: Displays the current number of active cores for the hard partition. In a virtual partition, the count represents the total number of cores assigned to all the virtual partitions. Inactive cores: Displays the current number of inactive cores in the hard partition. In a virtual partition, the count represents the total number of cores not assigned to any virtual partition. Inactive memory: Displays the current amount of inactive memory in the hard partition.
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.
iCAP HP-UX Manpages for HP Integrity Superdome 2 with Dynamic Cores 164 iCAP HP-UX Manpages for HP Integrity Superdome 2 with Dynamic Cores
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.
if the active Group Manager becomes unavailable for any reason. The field is displayed as N/A if no standby Group Manager is defined for the group. Borrowed/Loaned core usage rights: Identifies the count of core usage rights that were either borrowed from or loaned to the GiCAP group. This value must be 0 to remove the member from the GiCAP group. Borrowed/Loaned memory usage rights: Identifies the count of memory usage rights that were either borrowed from or loaned to the GiCAP group.
Available core temporary capacity: Displays the amount of core temporary capacity available. This balance is displayed in days, hours, and minutes. This value does not reflect any possible use of pooled temporary capacity from a GiCAP group, if the system is a member of a group. Warning period for core temporary capacity expiration: Displays the number of days constituting the core temporary capacity warning period for the complex.
Memory CR (Committed Rights): Displays the current amount of committed memory for the hard partition. Virtual Partition resource summary nPar ID: Displays the hard partition number of the virtual partition for the row of data. vPar ID: Displays the partition number of the virtual partition for the row of data. vPar name: Displays the partition name of the virtual partition for the row of data. vPar state: Displays the state of the partition. The possible states are “Active, SHUT, DOWN, and EFI”.
SEE ALSO icapmodify(1M).
icapmodify(1M) NAME icapmodify -- Activate and deactivate cores. Specify system contact email address. Change Instant Capacity configuration information. Specify system identifier. Specify temporary capacity warning period. Apply codewords. Specify temporary capacity pre-authorization.
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)).
NOTE: This option is not supported within a virtual partition. Deferred operations are not cumulative. If there is a pending deferred operation, a subsequent activation or deactivation request (-s, -a, or -d), deferred or not, cancels the pending deferred request and resets the values for intended active and actual active based on the request and the current value for actual active. 172 -i Set system identifier used during asset reporting.
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. If unused capacity is available, icapmodify will first activate cores from unused capacity before increasing the active cores.
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. • LC_TIME determines the date and time strings output. • LC_MESSAGES determines the language in which messages are displayed.
icapmodify -i Asset_Num_234 Set the system contact email address to super_user@corp.com: icapmodify -c super_user@corp.com Set the temporary capapcity pre-authorization flag on the Onboard Administrator: icapmodify -T on AUTHOR icapmodify was developed by HP. SEE ALSO icapstatus(1M), icapmanage(1M), icapd(1M), icap(5), vparmodify(1M).
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 blades, and memory that must remain inactive at all times.
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 are generated.
Virtual Partitions Dynamic core capabilities with vPars are supported from vPars A.05.09 or later. Instant Capacity can be present on 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).
nPartition of a group member to make assumptions that all cores might be active on another nPartition of the member. GiCAP GiCAP provides HP customers 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.
GiCAP group members Every operating system on a GiCAP group member must be running Instant Capacity version 10.04.01 or later. Every GiCAP group member must be hardware-compatible with other GiCAP group members, as determined by the GiCAP grouping rules. GiCAP grouping rules After you have determined which system will host the active Group Manager, you must acquire grouping rules from the portal and install the encrypted file on the active Group Manager system using the icapmanage -i command.
GiCAP member removal Before removing a member from a GiCAP group, all the borrowed usage rights must be returned, and all outstanding loans must be reclaimed. Borrowed usage rights are returned 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.
Group compliance When a group is out of compliance, the group is locked. Sharing of usage rights and temporary capacity among members of the group is not allowed, although members can return borrowed usage rights or reclaim loaned rights. Members cannot be added to the group, but members can be removed from the group if they deactivate any cores using borrowed usage rights and if GiCAP is able to reclaim any loaned usage rights.
rights can be added on both. In some cases, this can be valuable; for example, when each of the two data centers remain functional but some intervening network link is broken. Each isolated set of systems can proceed with independent disaster recovery operations within their group subset. At some point, communication is restored and the split groups are rejoined. This is accomplished through issuing a new icapmanage -Q command.
A Special Considerations This appendix covers the following topics: • “Assumed values in icapstatus command” (page 184) • “Upgrading to Instant Capacity version B.06.
If a nonlocal partition appears to be inactive, the number of active cores reported by the icapstatus command is zero. For example, if the hardware for a nonlocal partition is inactive, icapstatus considers the partition as inactive and reports the number of active cores as zero.
where codeword is the upgrade codeword that was supplied by the portal in step 4. This is easily accomplished by copying and pasting the codeword (that is generated by the portal) to the system where you are executing the icod_modify -C codeword command. The upgrade codeword needs to be applied only once on the entire system. 6. Install or upgrade all other partitions with the Instant Capacity B9073BA software (version B.06.00 or later).
• Load balancing across partitions • Configuring in virtual partitions 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), if 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.
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). These are the general rules the Instant Capacity software uses: • If the partition is to be shut down for less than 12 hours, no action is necessary.
psets on nPars In an nPar environment where psets are present, the Instant Capacity software activates and deactivates cores in only the default pset. Cores can be manually migrated to the default pset for purposes of deactivation, or from the default pset to other psets after activation. psets on vPars In a vPar environment, the Instant Capacity software passes the request for a core activation or deactivation to the vparmodify command. With vPars version A.04.
www.hp.com/go/bizsupport: • For HP-UX 11i v1: Installing and Administering Internet Services available at: www.hp.com/go/hpux-core-docs-11iv1 • For HP-UX 11i v2 and 11i v3: HP-UX Internet Services Administrator's Guide available at: www.hp.com/go/hpux-networking-docs On partitionable systems To enable asset reporting, configure email connectivity on each partition. This makes it easier to redistribute cores across partitions later (that is, load balance).
the receiving mail server at HP rejects the email. This field in the email can be configured with a simple one-line modification (DM) to the /etc/mail/sendmail.cf file. In some DNS environments, changes to the default /etc/mail/sendmail.cf file might not be needed to properly route email from the Instant Capacity system to HP. • In some environments, configuring your system to properly send email from the system to HP can require as little as a two-line edit (or none) to the /etc/mail/sendmail.cf file.
From email address is undesirable, you can configure the Instant Capacity software to use a From address you specify. Configuring a specified From Address To configure your specified Instant Capacity From email address, execute the following command: /usr/sbin/icapmodify -f from_address You can verify the configured Instant Capacity From email address by using the /usr/sbin/icapstatus command.
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.
notification email is sent. Also, other partition management software cannot determine whether the system contains iCAP components and, as a result, refuses to manage any components that are present. Customer security requirements The Instant Capacity software is designed to provide maximum protection for sensitive customer information. It follows these customer security requirements: • Sensitive customer data (names, phone numbers, email addresses, hostnames, IP addresses) is not transmitted to HP.
B Considerations for OpenVMS systems This appendix covers the following topics: • “CLI Support on OpenVMS” (page 195) • “DCL commands” (page 196) • “Special OpenVMS-Specific Features and Considerations” (page 199) • “Restrictions” (page 200) 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.
Table 14 HP-UX and OpenVMS command equivalents (continued) HP-UX Style icapmanage -r -g OpenVMS Style icap manage remove group icapmanage -T [,]...[-g icap manage test ] [/group=] icapmanage -a -m :[,]... -g icap manage add member /host_list=(host,host,...
Qualifiers Specifies the number of additional cores to activate. This qualifier is required. Defers the activation until the next reboot. (HP-UX equivalent: -D option) Authorize the use of temporary capacity to satisfy this activation request. (HP-UX equivalent: -t option) /CPU=n [/DEFER] [/TICAP] 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.
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. (HP-UX equivalent: icapnotify -a) Format ICAP SET ASSET [qualifier] Qualifiers /STATE=state: specify ON or OFF for the state qualifier value. EMAIL Sets the system contact email addresses.
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 Creates a string of snapshot information containing encrypted audit data and displays the string to the standard output device. (HP-UX equivalent: icapstatus -s) ICAP_SERVER Name ICAP_SERVER - iCAP server process.
Restrictions • Instant Capacity software on OpenVMS Version 8.4 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.
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, 36 virtual partition environment, 41, 42 Administration System, 12 asset report testing email transmission, 192 assigning cell to partition, 44 assumed values in icapstatus command, 184 audit application, 12 B boot time compliance, 43 boot time enforcement, 24 C cell assigning to partition, 44 unassigning from partition, 45 cell boards, 22 activating, 26, 59 cell removal implications, 187 cimconfig command, 29 cimserver command, 29 codewords, 23 applying, 21, 23, 35 TiCAP, 24 com
WBEM requirements, 65, 81 grouping rules, 23 H high availability, 64, 79 HP OpenView measurement software, 193 HP-UX reinstalling, 31 HP-UX 11i v1 requirements, 18 HP-UX 11i v2 requirements, 18 HP-UX 11i v3 requirements, 19 HPMC core failure and replacement, 47 I IAC see Instant Access Capacity iCAP audit application, 12 iCAP Cell Board, 59 accidental activation, 62 activating, 62 activation exception, 63 and TiCAP, 63 license and support, 60 ordering, 60 overview, 27, 59 usage rights, 60 usage rights exa
ICAP APPLY command, 197 ICAP DEACTIVATE command, 197 ICAP RECONCILE command, 197 ICAP SET command, 197 ICAP SHOW command, 199 ICAP_SERVER process, 199 restrictions, 200 special features and considerations, 199 system files, 196 OpenVMS considerations, 195 OpenVMS requirements, 20 overriding deferred activation, 39 overriding deferred deactivation, 39 P par commands with PC System Management Station, 188 parmodify command, 37 partitions shutting down, 37, 187 patches for HP-UX 11i v1, 18 for HP-UX 11i v2, 1
U unassigning cell from partition, 45 unused capacity, 42 upgrades GiCAP, 76 Instant Capacity version B.06.
