HP Instant Capacity Version 10.x User Guide (762794-001, March 2014)

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. When removing cores, icapmodify chooses cores only from the
default pset.
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.01 or later, vPars is pset-aware to some extent. When adding cores to
a running vPar, a core is always added to the default pset; thereafter, the core can be moved to
another pset. When removing cores, vparmodify chooses cores from the default pset first. If not
enough exist in the default pset to satisfy the request, vparmodify chooses the remaining cores
arbitrarily without regard to pset membership. In this case, with vPars version A.05.09 or later on
Superdome 2, vparmodify fails to delete the cores although it does not show any error message
as icapmodify does.
With vPars versions earlier than A.04, no special consideration is given to psets from the
vparmodify command’s perspective. Therefore, when using vPars, cores in nondefault psets must
be bound cores. Otherwise, a core designated for deactivation by vparmodify might be selected
from an unexpected pset.
Configuring email on Instant Capacity systems
Email requirements
Previous versions of the Instant Capacity software required email connectivity to HP to send asset
reports as encrypted email messages. Starting with version B.07.x, Instant Capacity software does
not require email connectivity or asset reporting. However, you can choose to configure it because
it can be useful for viewing complex-wide asset information at the HP Utility Pricing Solutions portal.
NOTE: Email asset reporting is set to “off” by default when the Instant Capacity software is
installed. You turn asset reporting on or off with the icapnotify -a command. You can view
the current setting of email asset reporting in the Asset reporting field, near the beginning of
the icapstatus command output.
The following are requirements for email connectivity:
• The Instant Capacity system or partition must have the sendmail utility installed and configured
so that it can send email to the hp.com domain.
• The domain name in the Instant Capacity FROM email address, for the email sent from the
Instant Capacity system to HP, must be DNS resolvable by HP. For details, see “Configuring
Instant Capacity’s From email address” (page 208).
IMPORTANT: On OpenVMS systems, SMTP mail must be configured for email connectivity. For
information about configuring SMTP mail, see the documentation for your TCP/IP provider.
Although the sendmail configuration and routing can vary, the system must have the ability to send
email to the hp.com domain.
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 209).
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. For
information, see the appropriate chapter in the following documents which are located on the HP
Documentation website:
206 Special Considerations