Upgrades and Global Instant Capacity

Care must be exercised before upgrading or changing hardware 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.

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. The problem can be resolved by purchasing and applying additional Sharing Rights to the Group Manager, purchasing and applying core usage rights (RTUs) to one or more group members, or by removing one or more group members from their group.

When such an incompatibility is detected, the GiCAP Group Manager sends e-mail to the local root account and to the registered contact e-mail address for each member of the group.

Adding New Partitions

When reconfiguring a member system by adding or deleting an nPartition, you must first remove the system from the group, and then re-add the member to the group (specifying the nPartition) after adding or deleting the nPartition. Also, if you wish to add additional contact points for a member system, you must remove and re-add the system to the group and specify additional hostnames for the system with the icapmanage -a -m command.

If the Group Manager is run on a partitionable system, changing the configuration of the partitions may result in the Group Manager becoming inoperative.