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.03.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, 2011 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..................................................................11 Instant Capacity Summary.......................................................................................................11 Terminology......................................................................................................................12 Overview..............................................................................................................................
3 Installing and Removing Instant Capacity Software........................................33 Installing Instant Capacity 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.................................................................................62 Temporary Capacity Enforcement.........................................................................................62 6 Instant Capacity Cell Board.......................................................................65 Instant Capacity Cell Board.........................
Resizing Partitions..............................................................................................................90 Memory iCAP...................................................................................................................91 Installing iCAP on HP Integrity Superdome 2..............................................................................91 iCAP commands..................................................................................................................
A Special Considerations...........................................................................157 Assumed Values in icapstatus Command.................................................................................157 Assumed Processor Values................................................................................................157 Assumed Memory Values..................................................................................................158 Upgrading to Instant Capacity version B.
Index.......................................................................................................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Instant Capacity System Elements.......................................................................................13 Permanent Activation of Instant Capacity 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 Undoing an Accidental Deferred Activation (HP-UX)..............................................................45 vPar Boot–Time Compliance Message.................................................................................49 Applying a Temporary Capacity Codeword (HP-UX).............................................................57 Activating an Instant Capacity Core with Temporary Capacity (HP-UX)....................................
1 Introduction to Instant Capacity This chapter covers the following topics: • “Instant Capacity Summary” (page 11) • “Overview” (page 12) For more in-depth information, see icap(5). Instant Capacity Summary HP Instant Capacity software provides the ability to instantly increase or decrease computing capacity on specified HP enterprise servers.
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 13) shows how the Instant Capacity system elements and processes are linked. Figure 1 Instant Capacity System Elements System Compliance iCAP DB Codeword Generation Record Purchase iCAP Admin System iCAP Web Portal 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 Global Instant Capacity groups (icapmanage command). For details about these commands on HP-UX, see “Instant Capacity HP-UX Manpages” (page 115). For the OpenVMS equivalents of these commands, see “DCL Commands” (page 170).
Most Recent Instant Capacity Product Versions and Supported Platforms Table 1 lists the current versions of Instant Capacity and the platforms supported for each version. Table 1 Most Recent Instant Capacity 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.03.00.
Table 1 Most Recent Instant Capacity 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 v2 • Superdome • Superdome B.11.23.10.00.01 • rx8640 • rp8420 (B9073BA) • rx8620 • rp8400 Available on: • rx7640 • rp7420 • http://www.hp.com/go/ softwaredepot • rx7620 • rp7410 • Superdome • Superdome B.11.23.10.00.
• 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.01 (on HP-UX 11i v1, 11i v2 and 11i v3) • B.08.02.00 (on HP-UX 11i v1, 11i v2 and 11i v3) • B.08.02.01 (on HP-UX 11i v1, 11i v2 and 11i v3) • B.08.03.00 (on HP-UX 11i v1, 11i v2, and 11i v3) • B.08.03.01 (on HP-UX 11i v1, 11i v2, and 11i v3) • 8.0 (on OpenVMS Version 8.3) • 9.0 (on HP-UX 11i v1, 11i v2, and 11i v3) • 9.
2 Getting Started This chapter covers the following topics: • “Instant Capacity Requirements” (page 19) • “Instant Capacity Components” (page 24) • “Global Instant Capacity” (page 25) • “Instant Capacity Codewords” (page 25) • “Temporary Instant Capacity” (page 26) • “Instant Capacity Compliance and Enforcement” (page 27) • “Configuration Change Notification” (page 27) • “Core Activation” (page 28) • “Instant Capacity Cell Board” (page 29) • “Instant Capacity Software Validation” (page 29
NOTE: For necessary HP-UX updates, install the latest Operating Environments Update Release (OEUR) or Application Release (AR) update, if possible. This ensures that you install all required products and versions. Instant Capacity does not work correctly with HP-UX releases prior to December 2004. Your Instant Capacity system is ordered and shipped with all of the following required software and dependent products, with the exception of the vPars software.
IMPORTANT: For the most recent required patches, see the Instant Capacity Installation page on the HP Software Depot (search for “B9073BA”): http://www.hp.com/go/softwaredepot HP-UX 11i v2 Requirements and Dependent Products The following software is required for Instant Capacity version 10.x on HP-UX 11i v2: • HP-UX 11i v2 • iCOD software bundle B9073BA (version 10.x) — On the 11i v2 Applications Software media, or download the most recent version from the HP Software Depot at:http:// www.hp.
• nParProvider bundle (version B.31.01.07.01 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.05.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.
NOTE: Starting with iCAP version 8.02, asset reporting is turned off by default for new installations. However, for reinstallation and upgrades the asset reporting remains at its previous setting; if your system was manufactured prior to iCAP version 8.02, asset reporting might still be turned on. Unless you turn off asset reporting or configure the email connectivity, error messages are logged when the software attempts to send asset reports.
Each of these versions provides a virtual partition environment which is tightly integrated with Instant Capacity, making it less likely for a complex to be misconfigured or to violate contractual compliance. The Instant Capacity software must be installed on all virtual partitions in an Instant Capacity system. For details about virtual partitions, see the Installing and Managing HP-UX Virtual Partitions manual on the Business Support Center (BSC) website: www.hp.
rights to enable all the memory attached to the cell. You cannot activate a cell board without activating all attached memory, so when you purchase an RTU for a cell you need to purchase an RTU for the cell’s memory. These are normally bundled together in a single purchase. Depending on the need, you might want to activate one or more cores at the same time the cell and memory are activated, so you might also need to acquire additional core usage rights.
purchasing codewords, see the Utility Pricing Solutions web portal information in “System Overview” (page 12). Once obtained from the portal, the rules and uses of GiCAP codewords are very different from other types of Instant Capacity codewords. The GiCAP codewords are described in “Global Instant Capacity Sharing Rights” (page 74) and are referred to as “GiCAP codewords”. Other types of codewords are referred to as “Instant Capacity codewords”.
Instant Capacity Compliance and Enforcement The Instant Capacity software primarily maintains complexwide information about the usage rights and activation of system components. The software monitors the number of usage rights for the entire complex for each type of component. (If you are using Global Instant Capacity, the software also maintains groupwide information about usage rights. For more information about GiCAP, see Chapter 7.
If you do not want an email notification to be sent when configuration changes are made, disable this feature by using the following command on HP-UX systems: /usr/sbin/icapnotify -n off Example 1 shows a configuration change email notification the Instant Capacity software sends to the system contact. Note that if the operation is a deferred configuration change, “previous” and “current” show equal values; only the value for “Number of cores to be active after reboot” reflects the requested change.
4. Activate a component. Depending on the type of component, do one of the following: • Activate a core in a hard partition (nPartition) by entering the icapmodify -a command. Note: For details about activating a core in a virtual partition, see “Instant Capacity Integration with Virtual Partitions (HP-UX)” (page 23). • Activate a cell board by using the parmodify or parmgr command. For details about activation of cell boards (and memory), see “Activation of an Instant Capacity Cell Board” (page 68).
iCOD B.11.23.09.00 HP-UX iCOD Instant Capacity To verify that the Instant Capacity software installation has not been corrupted, execute the following HP-UX command: /usr/sbin/swverify iCOD The command will display the message Verification succeeded. On OpenVMS Systems On OpenVMS systems, the Instant Capacity software is automatically installed on partitionable systems when the OpenVMS Version 8.3 or later operating system is installed.
@sys$manager:utc$time_setup “show”. Enter the command @sys$manager:utc$time_setup and follow the menu instructions to modify the time zone setting for the iCAP partition.
3 Installing and Removing Instant Capacity Software This chapter covers the following topics: • “Installing Instant Capacity Software” (page 33) • “Reinstalling Instant Capacity Software” (page 35) • “Removing Instant Capacity Software” (page 35) Installing Instant Capacity Software Factory Integrated Systems The Instant Capacity software is installed by HP on all HP enterprise servers, even those without Instant Capacity components.
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 Instant Capacity Software Preserving current Instant Capacity information If you reinstall HP-UX on a partition with Instant Capacity (for example, installing HP-UX by either cold-installing or installing from a golden image), you must perform the following steps. Otherwise, all information in the Instant Capacity configuration file (change history, system contact information) is lost.
4 Using Instant Capacity to Manage Processing Capacity This chapter covers the following topics: • “Checking the Status of your Instant Capacity 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)
• • • 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: Instant Capacity 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 Instant Capacity 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 Instant Capacity Components Customer Order iCAP System/ Components Apply IAC Codeword to System Additional Core Capacity Needed Consumption of IAC Halted Acquire IAC Codeword from Portal Activate Component(s) Using IAC Apply RTU Codeword to System Order iCAP RTU(s) Acquire RTU Codeword from Portal HP (or rep) Installs iCAP System/ Components HP Ship iCAP System/ Components Send Ack Letter Post IAC in iCAP DB Process Order for RTU(s) Post RTU Order in iCAP DB Ac
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 Instant Capacity 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 Instant Capacity software maintains a value for each nPartition of a complex called intended active. Fundamentally, the intended active value is the number of cores intended to be active after a reboot of the nPartition.
NOTE: Deferred activations and deactivations are not supported in any virtual partition environment. Instant Capacity always consumes unused capacity before it consumes additional usage rights when activating cores. Instant Capacity 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.
most 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 Instant Capacity 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.
to the icapstatus value for Additional cores that can be activated with current usage rights or the actual number of cores, whichever is smaller. In order 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 Cell 2 A 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 un
is required for activation of a core without usage rights for testing purposes. For details, see Chapter 5: “Temporary Instant Capacity” (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 Temporary Instant Capacity This chapter covers the following topics: • “Temporary Instant Capacity Overview” (page 55) • “Ordering Temporary Instant Capacity” (page 56) • “Using Temporary Instant Capacity” (page 57) • “Temporary Capacity and Virtual Partitions” (page 58) • “Tracking Usage of Temporary Instant Capacity” (page 59) • “Temporary Instant Capacity Warning Period” (page 60) • “Temporary Instant Capacity Expiration and Compliance Enforcement” (page 61) • “Temporary Instant Capacity
Figure 12 Using Temporary Instant Capacity: Temporary Activation of Cores Without Usage Rights Customer Order iCAP System/ Components HP (or rep) Installs iCAP System/ Components Prior to Needing Additional Core Capacity Order TiCAP Additional Core Capacity Needed Apply TiCAP Codeword to System Activate Core(s), with -t option Acquire TiCAP Codeword from Portal Deactivate Core(s) HP Ship iCAP System/ Components Send Ack Letter Process Order for TiCAP Post TiCAP Order in iCAP DB Ordering Temporar
OpenVMS Licensing and Support with Temporary Instant Capacity When you purchase temporary capacity, the temporary OpenVMS license-to-use is included when Instant Capacity cores are activated using temporary capacity. The OpenVMS License Management Facility recognizes when Temporary Instant Capacity 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 Instant Capacity Core with Temporary Capacity (HP-UX) > /usr/sbin/icapmodify -t -a 1 3 cores are intended to be active and are currently active. Number of cores using temporary capacity: 1 Projected temporary capacity exporation: 12/22/08 08:00:00 NOTE: Temporary capacity cannot be used to activate Instant Capacity cores in inactive Instant Capacity cell boards. You must purchase additional usage rights for the cell board and perhaps also for the memory of the cell board.
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.
Temporary Capacity Expiration Reminder The Instant Capacity 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 “Temporary Instant Capacity 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.
Temporary Instant Capacity Expiration and Compliance Enforcement IMPORTANT: If you leave cores without usage rights activated beyond the purchased temporary capacity duration, the software automatically deactivates one or more cores on the next reboot of any partition in the complex.
icapstatus output). When this state occurs, you need to take corrective action immediately by doing one of the following: • Deactivate Instant Capacity 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 Instant Capacity 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 Instant Capacity Cell Board This chapter covers the following topics: • “Instant Capacity Cell Board” (page 65) • “Ordering Instant Capacity Cell Board” (page 66) • “HP-UX and OpenVMS License and Support” (page 66) • “Acquiring Usage Rights for Instant Capacity Cell Board” (page 66) • “Instant Capacity Cell Board and Considerations of Core Usage Rights” (page 67) • “Activation of an Instant Capacity Cell Board” (page 68) • “Accidental Activation of an Instant Capacity Cell Board” (page 68) •
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 in order 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 in order 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.
Instant Capacity Cell Board Activation Exception Error When you attempt to activate an Instant Capacity cell board in an nPartition, depending on the number of core usage rights that are currently available in the complex, there is a chance the number of intended active cores for the nPartition is out of compliance and the activation fails. Figure 13, Figure 14, and Figure 15 illustrate this.
7 Global Instant Capacity This chapter covers the following topics: • “Global Instant Capacity Overview” (page 71) • “Global Instant Capacity Requirements” (page 72) • “Global Instant Capacity Group Managers” (page 73) • “Global Instant Capacity Grouping Rules” (page 74) • “Global Instant Capacity Sharing Rights” (page 74) • “Creating Global Instant Capacity Groups” (page 75) • “Global Instant Capacity Resource Sharing” (page 77) • “Global Instant Capacity and Temporary Capacity” (page 80) •
When you retrieve the codeword, you must provide the sales order number for the codeword purchase, the serial number of the Group Manager system, and partition information for the Group Manager. Applying this codeword on a system running Instant Capacity enables the creation of a GiCAP group with members. Figure 16illustrates the process of configuring and using Global Instant Capacity.
to the Group Manager system. GiCAP sharing rights are described in “Global Instant Capacity Sharing Rights” (page 74). For a complete list of all software requirements, see “Instant Capacity Requirements” (page 19). Global Instant Capacity Group Managers For each group, an HP-UX system must be designated as an active GiCAP Group Manager. This system maintains information about the group, group resources, and grouping rules. Use the icapmanage commands on a Group Manager system only.
The use of the icapmanage command is limited on a standby Group Manager. Only the -Q and -s options are allowed, all other options are restricted to use only on the active Group Manager. 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.
as there are sufficient sharing rights available, and as long as the grouping rules indicate hardware compatibility. Unlike other Instant Capacity codewords, GiCAP codewords must be generated for and applied to a specific partition if the Group Manager is on a partitionable system. This means that to retrieve the codeword, you must specify the purchase order number, the system serial number and partition information, if any.
You can create multiple GiCAP groups that can be managed by the same Group Manager or by different Group Manager systems. Systems with no any Instant Capacity components can be part of a GiCAP group. Deactivating resources on these systems allows them to loan usage rights to other members in the group. 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.
Between the time the core usage rights are made available and the Instant Capacity daemon monitors temporary capacity consumption, the icapstatus command reports that temporary capacity is 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.
Reinstalling a Group Member If a group member is reignited, use the icapmanage command as follows to reestablish communication between the newly ignited group member and the Group Manager: icapmanage -a -m : -g See the HP Instant Capacity Release Notes for more details about reestablishing SSL certificates.
standby status. Be aware that doing this loses all database changes made on the demoted Group Manager during the time that the group was split. There is no method to merge the two databases, and in particular any new sharing rights applied to the Group Manager designated now as standby are lost. Upgrades and Global Instant Capacity Be careful before upgrading or changing hardware or operating systems for any member of a GiCAP group.
core usage right per active cell. Any core usage rights in excess of this are made available for use elsewhere in the GiCAP group. The seizure of core usage rights from a fully unavailable member is temporary. After 10 days, the usage rights are automatically restored to the member from which they were seized. Seizure of core usage rights from a member with at least one accessible partition (at the time of rights seizure) do not expire.
Cells may be made inactive by removing them from the partition, shutting down the partition from within the OS by using shutdown -R -H, or with the MP RR command. If, at the time of rights seizure, all member partitions are unreachable, the rights seizure is deferred and must be viewed as a limited and immediate loan of usage rights from the specified partition to the group. This loan of seized usage rights expires in 10 days.
The Instant Capacity software determines that the partition is down based on whether the ping command is unsuccessful for the partition. In some circumstances, ping might be unsuccessful but the system remains functional (for example, if a network connection is interrupted). In this case, rights seizure may be inappropriate and leave workloads without the necessary resources. There are no restrictions regarding the type of environment from which rights were seized.
If a system cannot reconnect to the Group Manager within the 10-day period, you can extend the expiration of the seized usage rights. This extension is applied to the Group Manager through the use of a codeword obtained from HP support. • Core usage rights are always seized from the nPartition, even when the specified host is a virtual partition. • Usage rights can be seized from an nPartition only when: ◦ The nPartition is down.
Group Manager, the standby Group Manager functions as a standby for all the groups managed by that Group Manager. A server complex can be a member of only one GiCAP group at a time. To participate in a different group, it must be removed from one group before being added to the other group. Sharing rights can never be transferred between two active Group Manager systems.
8 Using Instant Capacity on HP Integrity Superdome 2 This chapter covers the following topics: • “Overview” (page 89) • “Important Considerations” (page 90) • “Installing iCAP on HP Integrity Superdome 2” (page 91) • “iCAP commands” (page 91) • “iCAP Use Cases” (page 94) Overview iCAP: From compliance check paradigm to self enforcement The Instant Capacity (iCAP) software on HP Integrity Superdome 2 does not perform a compliance check on the complex to check if the complex meets the iCAP contract.
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.
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.
Total number of configured cores: 16 Number of Intended Active cores: 11 Number of active cores: 11 Number of inactive cores: 5 Number of cores without usage rights: 5 Number of cores that could be activated with additional usage rights: 5 Number of cores that can be activated with temporary capacity: 5 Number of cores using temporary capacity: 0 Temporary capacity available: 5 days, 18 hours, 28 minutes(8308 minutes TiCAP ) Projected temporary capacity expiration: N/A Temporary capacity warning period: 15
Sample output: # 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.
iCAP Use Cases Core migration between partitions in a complex Active cores can be redistributed across any or all partitions of the complex if those partitions contain inactive cores. Consider a complex with 2 nPartitions, nPar1 and nPar2.
Table 7 Use Case 2 — Initial Configuration Partition Total Cores Total Active Cores nPar3 16 10 nPar4 8 8 Core migration from complex2 to complex1 may be done as follows: Choose a partition(s) in complex2 where you would like to reduce the active core count. In this use case, we have chosen nPar4. 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.
On npar1: # icapmodify -B 40000 Temporary capacity available: 27 days, 18 hours, 40 minutes(40000 minutes TiCAP) This assigns 40000 minutes of TiCAP to the partition npar1. NOTE: The amount of TiCAP is specified in minutes . It can also be specified in the ‘xxdyyhzzm’ that is for ‘xx’ days,’yy’ hours and ‘zz’ minutes. On npar2: # icapmodify -B 3200 Temporary capacity available: 2 days, 5 hours, 20 minutes(3200 minutes TiCAP) This assigns 3200 minutes of TiCAP to the partition npar2.
Using TiCAP balance to activate cores The available temporary capacity balance can be used to activate cores using the following command: icapmodify –a -t Sample Output: # icapmodify -a 2 -t 13 cores are intended to be active and are currently active.
TiCAP migration from npar 2 to npar1 can be done as follows: In npar2: #icapmodify –I -300 Temporary capacity available: 0 days, 5 hours, 0 minutes(300 minutes TiCAP ) In npar1: #icapmodify –I 300 Temporary capacity available: IMPORTANT: 0 days, 11 hours, 40 minutes(700 minutes TiCAP ) To remain in compliance, TiCAP decrement operation must be done first.
Partitions TiCAP Balance Npar1 200 minutes Npar2 500 minutes Complex2: Partitions TiCAP Balance Npar3 300 minutes Npar4 200 minutes Temporary Capacity (TiCAP) 99
9 Troubleshooting This chapter covers the following topics: • “Handling Compliance Exceptions” (page 101) • “Troubleshooting the Instant Capacity Software” (page 103) • “Diagnosing Email Configuration” (page 105) Handling Compliance Exceptions A complex can get out of compliance with the Instant Capacity contract if any of the following occurs: • More cells are active than expected (not enough inactive cells). • More memory is active than expected (not enough inactive memory).
Example 20 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 Instant Capacity contract, contact your local HP Response Center and request iCAP assistance. 4. Ensure that the required processes for Instant Capacity 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: • “Instant Capacity Software” (page 107) • “Instant Capacity Hardware” (page 110) • “Global Instant Capacity” (page 110) Instant Capacity Software What software product is required for Instant Capacity on Itanium-based servers running HP-UX? The HP software bundle for the Instant Capacity version 10.
• The Instant Capacity software sends an asset report to HP (daily at noon, if configured). • A partition with Instant Capacity is shut down. • A partition with Instant Capacity is started. • A partition with Instant Capacity 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 Instant Capacity log files in the /var/adm/icap.log or /var/ adm/icap.log.
Table 10 Email sent by the Instant Capacity software Triggered By Email Message icapmodify (if a configuration change occurs) Information about the configuration change is sent to the system contact, if specified, and if change notification is set to “on”. icapd (daily, when the projected TiCAP balance expiration is less than the warning period: by default, when less than 15 days) A temporary capacity expiration notification is sent to the system contact, if specified, and root.
Instant Capacity Hardware Can a faulty cell board be replaced with an inactive Instant Capacity cell board? Yes. 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. Global Instant Capacity Does HP know the configuration of the GiCAP groups? No. GiCAP group data is stored on the GiCAP Group Manager, which runs in the customer’s data center.
11 Support and other resources New and Changed Information in This Edition To review what is new and changed in this release of HP Instant Capacity, see the HP Instant Capacity Version 10.x Release Notes on the BSC website 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.
Location of Instant Capacity Information Instant Capacity Version 10.x user guide You can find the HP Instant Capacity Version 10.x user guide in the following locations: • On the BSC website: www.hp.com/go/hp-icap-docs These are the most current and the most current localized versions of the user guide. • March 2011 HP-UX 11i v3 Instant Information media (English, Simplified Chinese, and Japanese only) • In the Instant Capacity 10.x HP-UX software product: /usr/share/doc/icapRelNotes.
HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: docsfeedback@hp.com Include the document title, manufacturing part number, and any comment, error found, or suggestion for improvement you have concerning this document.
Instant Capacity HP-UX Manpages 115
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.
are made available through the HP Utility Pricing Solutions portal (http://www.hp.com/go/icap/ portal). Instant Capacity codewords (such as RTU codewords) are applied to a complex using the icapmodify command on any partition of the complex. iCAP codewords are generated with a sequence number, and all iCAP codewords for a particular complex must be applied in the order in which they were generated.
Virtual Partitions Instant Capacity has a minimum version dependency on vPars A.03.05. For versions of vPars before A.03.05, the icapmodify command for activating or deactivating cores in a virtual partition fails with an error message indicating the vPars version dependency. Instant Capacity can be present on systems or partitions where virtual partition technology is employed.
Whenever an Instant Capacity component without usage rights is purchased, an amount of Instant Access Capacity (IAC) might also be included. Instant Access Capacity is exactly the same as temporary capacity, except it is automatically provided with an Instant Capacity component and is not separately purchased.
GiCAP Group Manager For each group, an HP-UX system must be designated as an active Global Instant Capacity Group Manager. It is this system that maintains information about the group, group resources, and grouping rules. The icapmanage commands are intended to be used only on a Group Manager system to manage one or more GiCAP groups. The active Group Manager must be an HP-UX system running the Instant Capacity software version 9.0 or later.
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. GiCAP Group Creation After the sharing rights codeword and the grouping rules have been applied to the active Group Manager, a GiCAP group can be created by issuing the icapmanage command using the -a, -g and -m options.
Also, note that the number of available sharing rights is adjusted whenever an iCAP codeword is applied to a GiCAP member system which modifies the number of cores without usage rights on that member. (RTU and AddOn codewords for cores cause such adjustments.) If available sharing rights go negative (more in use than were purchased for the Group Manager), then all groups managed by that Group Manager are out of compliance and all group functions are restricted until the problem is resolved.
active Group Manager. For more details, see the “Group Manager Failover Considerations” section. Group Manager Failover Considerations If the active Group Manager system becomes unavailable, the standby Group Manager can take over GiCAP group operations from the Group Manager.
sslClientVerificationMode must be set to a value of “optional” on all GiCAP Group Managers and on all OS instances of all member systems. (The CIM Server may need to be restarted if the property was not previously set to this value.) For details, see cimconfig(1M). Note that communication between the managers and members of groups is established using SSL certificates that are supplied by the GiCAP software.
icapmanage(1M) NAME icapmanage -- Global Instant Capacity (GiCAP) management commands for GiCAP groups.
The icapmanage command can be used to install a grouping rules file, apply a GiCAP sharing rights codeword, create and remove GiCAP groups, test if a server can be added to a GiCAP group, update a GiCAP group by adding or removing members, show grouping rules and supported hardware, seize core usage rights from member partitions of a GiCAP group to be used by another member of the group, restore seized core usage rights to the original member partition, update an existing GiCAP member by adding or removing
-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) in order for the command to succeed.
When used in combination with the -S option, removes the identified host system from use as a standby Group Manager. -s Request status about one or more GiCAP groups. Specification without any additional options displays group and member information for all GiCAP groups managed by this Group Manager. Use the -g option to limit the information to the named group only. Use -b to display group-level information only.
-v Provide verbose status information. Include all levels of information (group, manager and member). For Group Managers, include resources being held by the Group Manager including temporary capacity. For members, include borrow and loan information as well as partition-specific information such as the allocation of resources among the hard partitions, and partition-specific information about seized or seizable usage rights (see icapmanage -x). This option is ignored if the -b option is also specified.
software, the unreachable partition may be assumed to be using all cores on cells configured for that partition. Because of this, cells in partitions from which usage rights have been acquired should be rebooted or made inactive within 12 hours. If this is not done, the partition can begin to consume temporary capacity. If temporary capacity is not available, the complex might no longer be in compliance with the iCAP contract.
To avoid this problem, usage rights must be restored (using the -z option) before failback. -z Restore previously seized core usage rights to the nPartition containing the specified host. Core usage rights must be available in the GiCAP group or the command fails.
established before the use of the icapmanage -Q command. Normally this occurs automatically when adding a new member to a group, updating the host list for an existing member, or adding a standby Group Manager. This command can be issued on an active Group Manager. In this case, the active Group Manager continues as the active Group Manager. It attempts to contact all group members and the previously active Group Manager and informs them that this system is the active Group Manager.
Group Manager, before or after groups are created). A Group Manager in standby status can be removed at any time. -T [,]... Test hardware compatibility for one or more host systems in order 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.
Number of inactive cells: This field displays the actual number of inactive cells across the group. It does not include counts for inactive cells associated with inaccessible members (no partitions could be contacted). Amount of memory without usage rights: This field 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: This field displays the actual amount of inactive memory across the group.
of usage rights that are not in use. This field is displayed only when the -v option is specified. Seized core usage rights: This summary field displays the number of expiring core usage rights that were seized from inaccessible members (see icapmanage -x). This field is displayed for all status options (-s, -b, -v), but only when usage rights were seized from member systems where none of the partitions could be contacted.
total for number of cores without usage rights includes last-known values for unreachable members. Additionally, information about rights seizure can be displayed for members where none of the partitions can be contacted: Seized core usage rights: This summary field displays the total number of expiring core usage rights that were seized from all partitions of this member (using icapmanage -x operations when none of the partitions could be contacted).
Expiration: This field displays the expiration date for core usage rights that were seized with icapmanage -x operations from the preceding named partition, or from the complex in the case of unassigned usage rights. The expiration date for a rights seizure operation effectively terminates the period during which the core usage rights are available to other group members for purposes of disaster recovery.
International Code Set Support Single- and multiple-byte character code sets are supported. RETURN VALUE icapmanage exits with one of these values: 0 Command succeeded. >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.
icapmanage -a -S mystandby.node.hp.com Remove host mystandby from use as a standby Group Manager: icapmanage -r -S mystandby.node.hp.com Take control as an active Group Manager: icapmanage -Q Show the full status of the ADMIN1 group: icapmanage -s -g ADMIN1 -v Seize core usage rights from a partition that is unavailable to make them available to other group member activations: icapmanage -x mypar1.node.hp.
icapmodify(1M) NAME icapmodify -- Activate and deactivate cores. Specify system contact email address. Change Instant Capacity configuration information. Specify Instant Capacity from email address. Specify system identifier. Specify temporary capacity warning period. Apply codewords.
Intended Active Changes to the number of intended active cores through the use of this command are persistent (survive system reboot). The intended active number is the number of cores that the Instant Capacity software attempts to activate at system boot time. It is adjusted by use of the -a, -d, and -s options. The number of intended active cores for each partition is displayed using the icapstatus command (see icapstatus(1M)).
-D 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.
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.
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.
exception reports for the local system. This field is set via the icapmodify -c command. From email: This field displays the email address that will be specified as the sender of all Instant Capacity initiated email correspondence for the local system. This field is set via the icapmodify -f command. If not set, email will be sent from the adm user on the local system.
Borrowed/Loaned memory usage rights: This field identifies the count of memory usage rights that were either borrowed from or loaned to the GiCAP group. This value must be 0 in order to remove the member from the GiCAP group. The output of icapstatus reflects the results of any GiCAP group operations: the borrowing or loaning of component usage rights or the transfer of temporary capacity.
group), even if the -t option is used with icapmodify for an activation. Number of cores currently unavailable for assignment: This field displays the number of unassigned cores in the hard partition that are not assigned to the local virtual partition and cannot be instantly assigned. This number includes cores in inactive cells and deconfigured cores. When using versions of vPars before A.03.
capacity balance, it may not be possible to activate all the inactive cores in a partition using temporary capacity. Also, temporary capacity is not used as long as there are available core usage rights on the complex, even if the -t option is used with icapmodify for an activation. This information is not displayed on a virtual partition. Number of cores that are deconfigured or attached to inactive cells: This field displays the number of cores that cannot be activated by Instant Capacity software.
capacity from a GiCAP group, if the system is a member of a group. Allocation of Instant Capacity Resources Among the nPartitions The following table displays how Instant Capacity components are distributed among the partitions in the complex: nPar ID: This field displays the partition number for the row of data. Total cores: This field displays the total number of cores physically present for the hard partition.
RETURN VALUE The icapstatus command exits with one of these values: 0 Command succeeded. 2 Command succeeded; system is not an Instant Capacity system. >0,!=2 Command failed; error message sent to STDERR. AUTHOR icapstatus was developed by HP. SEE ALSO icapmodify(1M), icapnotify(1M), icapmanage(1M), icapd(1M), icap(5).
icapd(1M) NAME icapd -- Instant Capacity (iCAP) daemon. SYNOPSIS icapd DESCRIPTION The icapd (formerly icodd) daemon is installed and started as part of the Instant Capacity software on all potential iCAP systems, and respawns itself if killed. If this daemon is not running, other Instant Capacity commands fail. The operations this daemon performs are vital in keeping the complexwide view of the Instant Capacity state current.
A Special Considerations This appendix covers the following topics: • “Assumed Values in icapstatus Command” (page 157) • “Upgrading to Instant Capacity version B.06.
NOTE: The number of active cores is always known for a local partition. 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.
5. Apply the upgrade codeword, generated by the Utility Pricing Solutions portal, to the system by executing this command: /usr/sbin/icod_modify -C codeword 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.
• Applying Right to Use (RTU) codewords • Activating and deactivating • 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), as long as there are enough available core, cell, and memory usage rights to cover activation of the cell, its memory, and at least one of the cores on the cell.
Shutting Down a Partition with Instant Capacity Cores The Instant Capacity software saves information about the number of active cores for each partition, and this information expires over time. If the partition is not active (but the hardware is powered up), Instant Capacity software on other partitions assumes that all cores in the inactive partition are active unless it can detect otherwise. For details about these assumed processor values, see “Assumed Values in icapstatus Command” (page 157).
NOTE: There must be at least one core in the default processor set. The last remaining core in the default processor set is unavailable for deactivation. Scope of the Instant Capacity Software Interacting with psets The Instant Capacity software does not provide any additional functionality to specifically support adding or removing cores from a specific pset.
The ability to receive email from HP is optional but is useful for testing the ability to send email to HP. For more information, see “Configuring Your Server to Send but Not Receive Email” (page 165). For more information about sendmail, see sendmail(1M). The sendmail utility is part of the HP-UX core and is installed with the HP-UX operating system. However, you must follow tha sendmail configuration process to complete its installation.
on the system queries a DNS server for the name of the email server to forward the email to (for the first hop) in order for the email to reach the final destination (hp.com). In all cases, the following requirements must be met: • HP mail servers that receive email expect the host (the mail server in the last hop before reaching HP) to be properly registered in DNS. If not, the HP mail server rejects, or “bounces”, the email.
The command in step 4 sends an email message to HP’s audit application. HP sends a confirmation email message to the reply_address. Receipt of the confirmation email message confirms successful email configuration. Configuring Instant Capacity’s From Email Address One of the email requirements of the Instant Capacity program is that the From email address, on email messages sent by the Instant Capacity software from your system, must be DNS resolvable. The Instant Capacity software uses adm@localhost.
Testing Email Transmission of the Asset Report NOTE: The following procedure assumes your Instant Capacity system is capable of sending internet email. Execute the following command to send your asset report by email to HP: /usr/sbin/icapnotify The specified reply_address receives an acknowledgment email from HP confirming the receipt of your asset report. Use an email client to verify the acknowledgment email from HP to the reply_address.
Security Issues Customer protections which iCAP assumes to be in place Instant Capacity commands provide system status information and facilitate system configuration modification, and are therefore executable only by users with root level access. An assumption is made that there exist administrative policies which exercise the appropriate degree of control over root level access.
B Considerations for OpenVMS Systems This appendix covers the following topics: • “CLI Support on OpenVMS” (page 169) • “DCL Commands” (page 170) • “Special OpenVMS-Specific Features and Considerations” (page 173) • “Restrictions” (page 174) 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 174 • 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, 14 asset report testing email transmission, 166 assigning cell to partition, 49 assumed values in icapstatus command, 157 audit application, 14 B boot time compliance, 48 boot time enforcement, 27 C cell assigning to partition, 49 unassigning from partition, 50 cell boards, 24 activating, 29, 65 cell removal implications, 160 cimconfig command, 33 cimserver command, 33 codewords, 25 applying, 23, 26, 40 TiCAP, 26 com
WBEM requirements, 72, 88 Global Instant Capacity see GiCAP grouping rules, 25 H high availability, 71, 86 HP OpenView measurement software, 166 HP-UX reinstalling, 35 HP-UX 11i v1 requirements, 20 HP-UX 11i v2 requirements, 21 HP-UX 11i v3 requirements, 21 HPMC core failure and replacement, 52 I IAC see Instant Access Capacity ICAP_SERVER time zone, 30 icapd daemon time zone, 30 icapmanage command, 73 adding group members, 76 adding partitions, 83 creating groups, 75 installing grouping rules, 74 removin
ICAP ACTIVATE command, 170 ICAP APPLY command, 171 ICAP DEACTIVATE command, 171 ICAP RECONCILE command, 171 ICAP SET command, 171 ICAP SHOW command, 173 ICAP_SERVER process, 173 restrictions, 174 special features and considerations, 173 system files, 170 OpenVMS considerations, 169 OpenVMS requirements, 22 overriding deferred activation, 44 overriding deferred deactivation, 44 P par commands with PC System Management Station, 161 parmodify command, 42 partitions shutting down, 42, 161 patches for HP-UX 11i
Instant Capacity software, 103 U unassigning cell from partition, 50 unused capacity, 47 upgrades GiCAP, 83 Instant Capacity version B.06.
