HP Instant Capacity Version 10.x User Guide (5900-2170, January 2012)

A Special Considerations
This appendix covers the following topics:
• “Assumed values in icapstatus command” (page 189)
• “Upgrading to Instant Capacity version B.06.x or later (HP-UX)” (page 190)
• “Dual-core support in Instant Capacity systems” (page 191)
• “New partition creation and Instant Capacity” (page 192)
• “Implications of removing a cell from an Instant Capacity system ” (page 192)
• “Shutting down a partition with Instant Capacity cores” (page 192)
• “Instant Capacity and reinitializing the nPartition (Genesis Partitions)” (page 193)
• “par Commands from PC System Management Station” (page 193)
• “Instant Capacity compatibility with Processor Sets (HP-UX)” (page 193)
• “Configuring email on Instant Capacity systems” (page 194)
• “Measurement software and Instant Capacity systems” (page 198)
• “Dynamic processor resilience (HP-UX)” (page 198)
• “Security issues” (page 198)
Assumed values in icapstatus command
The icapstatus command might make assumptions on the number of active cores and amount
of active memory, depending on certain system conditions. If values are assumed, the icapstatus
command output contains an asterisk next to the appropriate field.
Assumed processor values
Occasionally, the output of the icapstatus command contains an asterisk (*) next to the value
in the Actual Active Cores field (under the section Allocation of Instant Capacity
Resources among the nPartitions). The asterisk appears in the output whenever a nonlocal
partition appears to be active, but the icapd daemon is not reporting system information. Some
examples that can cause this situation include:
• The absence of a compatible version of the Instant Capacity software on a nonlocal partition
• No space left in /var on the nonlocal partition prevents icapd from communicating system
information
• A nonlocal partition shut down for an extended period of time with shutdown or reboot,
without the -R -H options (which brings the cells to an inactive state)
• A nonlocal partition running an operating system that is not HP-UX or OpenVMS (for example,
Windows or Linux)
In these cases, the Instant Capacity software on other partitions identifies all cores in the nonlocal
partition as active. In addition to the asterisks in the output of icapstatus, this can affect the
following:
• TiCAP consumption
• The ability to change the complex with parmodify, parmgr, or parcreate commands
• Core activation with the icapmodify command
• System noncompliance
NOTE: The number of active cores is always known for a local partition.
Assumed values in icapstatus command 189