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.05.00.03 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, 2012 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..................................................................13 Instant Capacity summary........................................................................................................13 Terminology......................................................................................................................14 Overview..............................................................................................................................
3 Installing and removing iCAP software........................................................33 Installing iCAP software...........................................................................................................33 Installing from the HP-UX media (HP-UX 11i v1, 11i v2, and 11i v3):..........................................33 Installing from the HP Software Depot (For HP-UX 11i v1, 11i v2, and 11i v3):.............................34 For All HP-UX installations................................
Temporary capacity balance needing action.........................................................................61 Temporary capacity negative balance................................................................................107 Temporary capacity enforcement........................................................................................107 6 iCAP cell board.......................................................................................65 iCAP cell board...............................
Sizing partitions............................................................................................................90 Resizing partitions.........................................................................................................90 Memory iCAP...............................................................................................................91 Installing iCAP on HP Integrity Superdome 2.........................................................................
TiCAP exceptions........................................................................................................107 Error for activation with insufficient TiCAP..................................................................107 TiCAP negative balance..........................................................................................107 TiCAP enforcement.................................................................................................107 GiCAP...................................
iCAP(5)...............................................................................................................................181 A Special Considerations...........................................................................189 Assumed values in icapstatus command...................................................................................189 Assumed processor values.................................................................................................189 Assumed memory values.
Glossary..................................................................................................207 Index.......................................................................................................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 iCAP system elements.......................................................................................................15 Permanent activation of iCAP components...........................................................................41 Partition premodification state: One cell assigned with 3 active and 1 inactive cores, and usage rights for 2 additional cores............................................................................................
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Undoing an accidental deferred activation (HP-UX)...............................................................45 vPar Boot–Time compliance message..................................................................................49 Applying a TiCAP codeword (HP-UX)..................................................................................57 Activating an iCAP Core with TiCAP (HP-UX)................................................................
1 Introduction to Instant Capacity This chapter covers the following topics: • “Instant Capacity summary” (page 13) • “Overview” (page 14) 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.
except it is automatically provided with an iCAP component and cannot be purchased 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.
Figure 1 (page 15) 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 129). For the OpenVMS equivalents of these commands, see also “DCL commands” (page 202).
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.05.00.
Table 1 Most recent iCAP versions and supported platforms (continued) 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.02.00.00 • Superdome • rp8440 (B9073BA) • rx8640 • rp8420 Available on: • rx8620 • rp8400 • http://www.hp.com/go/ softwaredepot • rx7640 • rp7440 • rx7620 • rp7420 • rp7410 • HP Integrity Superdome 2 • Superdome B.11.31.10.
Table 1 Most recent iCAP versions and supported platforms (continued) Software and version Operating System version Supported hardware platform — Supported hardware platform — HP Integrity HP 9000 iCAP HP-UX 11i v1 Not supported. • Superdome B.11.11.09.02.00 • rp8440 (B9073BA) • rp8420 Available on: • rp8400 • http://www.hp.com/go/ softwaredepot • rp7440 • September 2009 HP-UX 11i v1 Applications Software media • rp7410 iCAP 9.x (BA484AA) • rp7420 HP OpenVMS Version 8.
• 9.02 (on HP-UX 11i v1, 11i v2, and 11i v3) • 9.
2 Getting Started This chapter covers the following topics: • “iCAP requirements” (page 21) • “iCAP components” (page 25) • “GiCAP” (page 26) • “iCAP codewords” (page 27) • “TiCAP” (page 27) • “iCAP compliance and enforcement” (page 28) • “Configuration change notification” (page 29) • “Core activation” (page 30) • “iCAP cell board” (page 31) • “iCAP software validation” (page 31) • “Status reporting on iCAP systems” (page 32) • “Time zone considerations” (page 32) 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. • (GiCAP only) The CIM Server configuration property sslClientVerificationMode must be set to a value of “optional” on all GiCAP Group Managers and on all OS instances of all member systems.
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 74).
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 71). 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 boot time: ◦ Automatically deactivate cores at 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 61)).
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.
On OpenVMS systems On OpenVMS systems, the iCAP software is automatically installed on partitionable systems when the OpenVMS Version 8.3 or later operating system is installed. You should not need to install the 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.
3 Installing and removing iCAP software This chapter covers the following topics: • “Installing iCAP software” (page 33) • “Reinstalling iCAP software” (page 35) • “Removing iCAP software” (page 35) Installing iCAP software Factory Integrated Systems The iCAP software is installed by HP on all HP enterprise servers, even those without iCAP components.
4. 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. Continue with “For All HP-UX installations” (page 34). Installing from the HP Software Depot (For HP-UX 11i v1, 11i v2, and 11i v3): 1.
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 37) • “Setting system contact information” (page 39) • “Applying a Right To Use (RTU) codeword” (page 40) • “Activating Cores” (page 41) • “Deactivating cores” (page 43) • “Overriding deferred activation and deactivation” (page 44) • “Load-balancing active cores” (page 45) • “Understanding and managing intended active values” (page 46) • “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 55). 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. 2. 3. 4. 5. 6. 7. 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.
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 55) • “Ordering TiCAP” (page 56) • “Using TiCAP” (page 57) • “TiCAP and vPars” (page 58) • “Tracking usage of TiCAP” (page 59) • “TiCAP warning period” (page 60) • “TiCAP expiration and compliance enforcement” (page 61) • “TiCAP exceptions” (page 61) 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 60)), 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 65) • “Ordering iCAP cell board” (page 66) • “HP-UX and OpenVMS license and support” (page 66) • “Acquiring usage rights for iCAP cell board” (page 66) • “iCAP cell board and considerations of core usage rights” (page 67) • “Activation of an iCAP cell board” (page 68) • “Accidental activation of an iCAP cell board” (page 68) • “iCAP cell board activation exception error” (page 69) • “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 49) and “Unassigning a cell from a partition” (page 50).
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. 2. Acquire the appropriate RTU codeword (cell board, memory, core) from the Utility Pricing Solutions portal (http://www.hp.com/go/icap/portal). 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 71) • “GiCAP requirements” (page 72) • “GiCAP Group Managers” (page 73) • “GiCAP grouping rules” (page 74) • “GiCAP sharing rights” (page 74) • “Creating GiCAP groups” (page 75) • “GiCAP resource sharing” (page 77) • “GiCAP and temporary capacity” (page 80) • “Removing a GiCAP group member” (page 81) • “Reinstalling a group member” (page 81) • “Group Manager availability (no standby manager)” (page 82) • “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.
Example 17 Creating a group > icapmanage -a -g one Group one added. > icapmanage -s Software version: B.09.00 32 GiCAP Sharing Rights: 0 in use, 32 available Group ID: one Group Members: No members found Example 18 updates the grouping rules for all groups managed by the Group Manager, tests whether a server complex has hardware compatible with group “one”, and adds a member called “IT” to that group. When you first add new members to a group, you are prompted for the root password for each specified host.
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.
being consumed when it is not. When the transfer of usage rights is completed, the icapstatus 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.
icapmanage -a -m : -g 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.
date for a rights seizure operation effectively terminates the period during which the core usage rights are available to other group members for purposes of disaster recovery. 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.
There are no restrictions regarding the type of environment from which rights were seized. Rights that are seized from either an nPartition environment or a virtual partition environment can be deployed on any member of the GiCAP group, regardless of the target environment type.
• Usage rights can be seized from an nPartition only when: ◦ The nPartition is down. ◦ Assuming the nPartition is hosting virtual partitions, all the virtual partitions are down. 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 on each nPartition in the server.
Sharing rights can never be transferred between two active Group Manager systems. As you create new groups or add new members to existing groups, you might need to purchase and apply additional sharing rights to the relevant active Group Manager systems. This is necessary even if the member has been moved from another Group Manager that now has excess sharing rights. Sharing rights can never be applied to a Group Manager with standby status.
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 99).
1. Go to the HP Utility Pricing Portal at www.hp.com/go/icap/portal. This portal handles all of the iCAP transactions. 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.
Memory iCAP The iCAP memory is available on HP Integrity Superdome 2 servers. The iCAP offering on memory is very similar to the current iCAP offering. You can purchase an HP Integrity Superdome 2 cell blade with all iCAP memory or all active memory. All 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.
Number of Number of Number of Number of Number of Number of Number of Temporary Projected Temporary Intended Active cores: 11 active cores: 11 inactive cores: 5 cores without usage rights: 5 cores that could be activated with additional usage rights: 5 cores that can be activated with temporary capacity: 5 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 s
# icapmodify -d 1 3 cores are intended to be active and are currently active. Activating cores Cores can be dynamically activated on a partition to address any additional demand. As mentioned before, iCAP does not perform any compliance check to see if the total active cores exceed the total usage rights purchased. It is required that the cores should be available to the partition for activating them.
Consider a complex with 2 nPartitions, nPar1 and nPar2. Table 4 displays the Initial Configuration of the complex: 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.
In nPar4: # 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 -t Sample Output: #icapmodify -d 2 11 cores are intended to be active and are currently active.
Npar1 700 minutes 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. 2. Select partition(s) in complex 1 to decrement the TiCAP Balance. Here we select npar1.
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.
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.
Available core temporary capacity : 2 days, 20 hours, 30 minutes 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.
more cores than are configured into the current virtual partition, but only if the associated nPartition 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.
Tracking usage of TiCAP The icapstatus command provides the following information about the use of temporary capacity on the system: • Amount of temporary capacity remaining (in days, hours, and minutes) • Number of cores using temporary capacity (number of active cores without usage rights) • Projected temporary capacity expiration date and time (based on the current temporary capacity consumption rate) You can find this information in the Summary of iCAP contract section of the icapstatus command ou
Temporary capacity is audited at the complex level on iCAP systems that support partitioning and are not part of a GiCAP group. Although temporary capacity might have been purchased for use by a specific partition, it is available to all partitions in the complex (or to the entire GiCAP group, if applicable). TiCAP exceptions Error for activation with insufficient TiCAP You cannot activate an iCAP core with temporary capacity unless there is a sufficient balance of temporary capacity available.
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: The requirements are applicable for both active and standby Group Managers. Configuration Requirements on managed HP Integrity Superdome 2 systems To add an HP Integrity Superdome 2 system into a GiCAP group, the following requirements must be met by the Onboard Administrator associated with the HP Integrity Superdome 2 system. • The Onboard Administrator must support the dynamic cores feature. • HTTPS must be enabled on the Onboard Administrator associated with the group member.
icapmanage -C #icapmanage -C dQzFA8u.hCYhGYF.Wn738Lh.55ritjN.2-1HiMMGV.TgyrueW.D5sUyE2.PstMAg4 The following valid codeword has been applied to the GiCAP manager: Global Instant Capacity Sharing Rights Codeword For SD2 40 Sharing Rights Use icapmanage(1M) to see the results of the application of this codeword.
The following example shows how to remove an HP Integrity Superdome 2 system from the group: # icapmanage -r -m complex_abc Member complex_abc removed.
# 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 115) • “Troubleshooting the iCAP software” (page 117) • “Diagnosing email configuration” (page 119) 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.
Diagnosing email configuration Follow these steps to confirm the email configuration or to aid in debugging the configuration: 1. 2. 3. 4. Send an email message from your system to an email address in the same domain (intranet) and confirm receipt of the email message. Send an email message from your system to an email address outside of your domain (to the internet, for example, to a yahoo or hotmail email address) and confirm receipt of the email message.
10 Frequently asked questions This chapter covers frequently asked questions on the following topics: • “iCAP software” (page 121) • “iCAP hardware” (page 124) • “GiCAP” (page 124) 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 v1, 11i v2, or 11i v3, is HP product number B9073BA.
• A partition with iCAP is started. • 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 124)).
Table 10 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.
Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document.
iCAP HP-UX Manpages for HP Integrity Superdome 2 129
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.
icapmanage commands are intended to be used only on a Group Manager system to manage one or more GiCAP groups. The active Group Manager must be an HP-UX system running the Instant Capacity software version 9.0 or later. The system running the Group Manager does not need to have any Instant Capacity 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.
GiCAP Group creation After the sharing rights codeword and the grouping rules are applied to the active Group Manager, a GiCAP group can be created by issuing the icapmanage command using the -a, -g and -m options. Members are added by issuing the icapmanage command using the -a option, the -g option to select the group name, and the -m option to specify a name for the new member along with a list of hosts running on the system.
are restricted until the problem is resolved. The problem can be resolved by purchasing and applying additional sharing rights to the Group Manager, by purchasing and applying core usage rights to one or more group members, or by removing one or more group members from their group.
the standby Group Manager are unavailable, or if the active Group Manager fails and the icapmanage -Q command was not issued to make the standby Group Manager the active Group Manager, usage rights and temporary capacity remain as per allocated to each group member. Within a server complex, the usage rights can be deployed to other partitions, but movement of usage rights and temporary capacity between complexes cannot occur.
exception is that the number of active cores is allowed to exceed the number of core usage rights if there is a sufficient positive balance of temporary capacity. A negative balance always indicates a system which is out of compliance.
icapmanage(1M) NAME icapmanage -- GiCAP management commands for GiCAP groups.
The icapmanage command can be used to install a grouping rules file, apply a GiCAP sharing rights codeword, create and remove GiCAP groups, test if a server can be added to a GiCAP group, update a GiCAP group by adding or removing members, show grouping rules and supported hardware, seize core usage rights from member partitions of a GiCAP group to be used by another member of the group, restore seized core usage rights to the original member partition, update an existing GiCAP member by adding or removing
-m Add a member (a partitionable complex) to a group, with :[,]... name member_name. Specify an OS instance (host) for each nPartition or virtual partition of the complex (do not specify virtual machine or guest OS instances). A member of a group must encompass all nPar and vPar OS instances of a complex, and each OS instance specified as a host must be accessible, (ping-able) for the command to succeed.
When used in combination with the -S option, removes the identified host system from use as a standby Group Manager. -s Request status about one or more GiCAP groups. Specification without any additional options displays group and member information for all GiCAP groups managed by this Group Manager. Use the -g option to limit the information to the named group only. Use -b to display group-level information only.
-v Provide verbose status information. Include all levels of information (group, manager and member). For Group Managers, include resources being held by the Group Manager including temporary capacity. For members, include borrow and loan information and partition-specific information, such as the allocation of resources among the hard partitions, and partition-specific information about seized or seizable usage rights (see icapmanage -x). This option is ignored if the -b option is also specified.
cores on cells configured for that partition. Because of this, cells in partitions from which usage rights have been acquired should be rebooted or made inactive within 12 hours. If this is not done, the partition can begin to consume temporary capacity. If temporary capacity is not available, the complex might no longer be in compliance with the iCAP contract.
-z Restore previously seized core usage rights to the nPartition containing the specified host. Core usage rights must be available in the GiCAP group or the command fails. This option can be useful particularly when core usage rights are seized from systems running vPars, because the restoration of core usage rights might be necessary to be able to reboot the vPar, depending on the vPars database definition and the allocation of usage rights among the vPars.
group, updating the host list for an existing member, or adding a standby Group Manager. This command can be issued on an active Group Manager. In this case, the active Group Manager continues as the active Group Manager. It attempts to contact all group members and the previously active Group Manager and informs them that this system is the active Group Manager. This is useful if a previous icapmanage -Q command failed to contact some group members or the previously active Group Manager.
Group Manager in standby status can be removed at any time. -T [,]... Test hardware compatibility for one or more host systems to determine which groups the systems can join. When used with the -g option to specify a group name, tests whether the specified host systems have hardware compatible with the group. Without the -g option, reports which groups managed by this Group Manager have hardware compatible with the host systems.
inactive cells associated with inaccessible members (no partitions could be contacted). Amount of memory without usage rights: Displays the total amount of memory which must remain inactive across all group members because usage rights have not been purchased. Amount of inactive memory: Displays the actual amount of inactive memory across the group. It does not include counts for inactive memory associated with inaccessible members (no partitions could be contacted).
usage rights were seized from member systems where none of the partitions could be contacted. Expiration of seized core usage rights: Displays the earliest expiration date for core usage rights that were seized from members where none of the partitions could be contacted (see icapmanage -x). The expiration date for a rights seizure operation effectively terminates the period during which the core usage rights are available to other group members for disaster recovery.
-x operations when none of the partitions could be contacted). This member summary field is not displayed when the -v option is specified (because the -v option includes a detailed list instead). Expiration of seized core usage rights: Displays the earliest expiration date for core usage rights that were seized from all partitions of this member (using icapmanage -x operations).
available to other group members for purposes of disaster recovery. Displayed only when the -v option is specified and only for systems where usage rights were seized for disaster recovery, if none of the member partitions could be contacted. Guidelines for interpretation of Usage Rights Counts In general, the Instant Capacity software is designed to enforce the cpt that a certain number of resources must remain inactive to stay in compliance with the iCAP contract.
>0 Command failed; error message sent to STDERR. FILES /var/adm/GiCAP.log Log file for GiCAP operations and messages. /etc/opt/iCAP/GiCAP.rules Encrypted file containing grouping rules used by the Group Manager. /etc/opt/iCAP/GiCAP_db Encrypted file containing information about sharing rights and information about each group managed by the Group Manager. /etc/opt/iCAP/GiCAP.configFile Present on every host of a GiCAP group member.
icapmanage -Q Show the full status of the ADMIN1 group: icapmanage -s -g ADMIN1 -v Seize core usage rights from a partition that is unavailable to make them available to other group member activations: icapmanage -x mypar1.node.hp.com Restore previously seized usage rights to the partition from the previous example: icapmanage -z mypar1.node.hp.com Report supported hardware and grouping rules for a specific grouping rules file: icapmanage -R -U /tmp/GiCAP.
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 -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 169
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.
Group Manager has the ability to take control of the group 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.
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.
Cores AA (Actual Active Cores): Displays the current number of active cores for the hard partition. Cores CR (Committed Rights): Displays the current number of committed cores for the hard partition. Memory IA (Intended Active Memory): Displays the amount of memory requested to be active for the hard partition; this is the amount of memory that will be activated during a boot operation. Memory Tot (Total Memory): Displays the total amount of memory physically present for the hard partition.
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_TIME determines the date and time strings output. • LC_MESSAGES determines the language in which messages (other than the date and time strings) are displayed.
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. -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 -c super_user@corp.com Set the temporary capapcity pre-authorization flag: 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 Instant Capacity has a minimum version dependency on vPars A.03.05. For versions of vPars before A.03.05, the icapmodify command for activating or deactivating cores in a virtual partition fails with an error message indicating the vPars version dependency. Instant Capacity can be present on systems or partitions where virtual partition technology is employed.
amount of temporary capacity time remaining on a complex can be obtained by executing the icapstatus command. A warning is also sent via email when the temporary capacity balance is expected to be depleted within a certain period of time. The icapmodify command allows you to activate a core using temporary capacity only if at least 30 minutes of temporary capacity is available for each core that is being activated.
Standby GiCAP Group Manager The active GiCAP Group Manager can designate a standby Group Manager. This standby Group Manager can take control of GiCAP group management from the active Group Manager using the command icapmanage -Q. This allows GiCAP group operations to continue if the GiCAP Group Manager is unable to function. Note that the requirements and recommendations defined for the Group Manager also apply to the standby Group Manager; it is a Group Manager with standby status.
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. In effect, the system on which the resources were deactivated is loaning usage rights to the activating (or borrowing) system.
Because group members are automatically considered to be users of temporary capacity, to avoid unexpected TiCAP depletion in a group, it is important to avoid the situations that cause the Instant Capacity software to make assumptions that all cores might be active on a remote nPartition, as described previously in the TiCAP section.
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. This is referred to as a bifurcated (or split) GiCAP group. Reachable members start accepting commands from the standby Group manager while unreachable members continue to consider the previous Group manager active.
A Special Considerations This appendix covers the following topics: • “Assumed values in icapstatus command” (page 189) • “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 189). 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.
• 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). For details, see “Load-balancing active cores” (page 45).
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.
Note that disabling the daemon in this way on an iCAP or GiCAP system is a violation of the iCAP contract with HP. After 12 to 24 hours, the system goes out of compliance and an exception 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.
B Considerations for OpenVMS systems This appendix covers the following topics: • “CLI Support on OpenVMS” (page 201) • “DCL commands” (page 202) • “Special OpenVMS-Specific Features and Considerations” (page 205) • “Restrictions” (page 206) 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 13 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, 41 virtual partition environment, 46, 47 Administration System, 16 asset report testing email transmission, 197 assigning cell to partition, 49 assumed values in icapstatus command, 189 audit application, 16 B boot time compliance, 48 boot time enforcement, 28 C cell assigning to partition, 49 unassigning from partition, 50 cell boards, 26 activating, 30, 65 cell removal implications, 192 cimconfig command, 33 cimserver command, 33 codewords, 27 applying, 25, 27, 40 TiCAP, 28 com
WBEM requirements, 72, 88 grouping rules, 27 H high availability, 71, 86 HP OpenView measurement software, 198 HP-UX reinstalling, 35 HP-UX 11i v1 requirements, 22 HP-UX 11i v2 requirements, 22 HP-UX 11i v3 requirements, 23 HPMC core failure and replacement, 52 I IAC see Instant Access Capacity iCAP audit application, 16 iCAP Cell Board, 65 accidental activation, 68 activating, 68 activation exception, 69 and TiCAP, 69 license and support, 66 ordering, 66 overview, 31, 65 usage rights, 66 usage rights exa
ICAP APPLY command, 203 ICAP DEACTIVATE command, 203 ICAP RECONCILE command, 203 ICAP SET command, 203 ICAP SHOW command, 205 ICAP_SERVER process, 205 restrictions, 206 special features and considerations, 205 system files, 202 OpenVMS considerations, 201 OpenVMS requirements, 24 overriding deferred activation, 44 overriding deferred deactivation, 44 P par commands with PC System Management Station, 193 parmodify command, 42 partitions shutting down, 42, 192 patches for HP-UX 11i v1, 22 for HP-UX 11i v2, 2
U unassigning cell from partition, 50 unused capacity, 47 upgrades GiCAP, 83 Instant Capacity version B.06.
