HP Instant Capacity (iCAP) manual Additional Considerations

Additional Considerations

Systems that do not have 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.

Members of a GiCAP group do not have to be located near each other. IP connectivity between the members, the Group Manager, and the standby Group Manager (if any), sufficient GiCAP sharing rights, and adherence to the GiCAP grouping rules are the only constraints.

For systems with multiple network cards, you can specify the additional network paths as additional hosts when defining member systems in a group, for enhanced connectivity. However, there might be a significant performance penalty because the Instant Capacity software occasionally must access all the multiple hosts in that case. You cannot specify the Group Manager and the standby Group Manager such that they are different network paths to the same system. An OS instance can host one and only one GiCAP database, regardless of the number of hostnames by which that OS instance might be reachable.

WBEM version A.02.05 or higher must be installed on the Group Manager and on all member systems in order to use Global Instant Capacity. 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. (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.

If the GiCAP Group Manager system becomes unavailable, the standby GiCAP Group Manager can take over GiCAP group operations from the Group Manager. If both the Group Manager and the standby Group Manager are unavailable, usage rights and temporary capacity remain as allocated to each group member. Within a server complex, the usage rights can be deployed to other partitions, but movement of usage rights between complexes cannot occur.

On a system with full usage rights, the icapd daemon does not constantly verify the system configuration. It can take up to 12 hours for each partition of a system converted from non-iCAP to iCAP to discover that it is now an iCAP system. During this time, icapmanage -sshows asterisks for the new member, and the icapstatus command issued on that system shows “Runs iCAP” as “N”. To force a faster conversion, kill the icapd daemon and wait for it to restart.

128 Global Instant Capacity