Power Enterprise Pool

You can move Mobile CoD resource activations among the systems in a pool with Hardware Management Console (HMC) commands. These operations provide flexibility when you manage large workloads in a pool of systems and helps to rebalance the resources to respond to business needs. This feature is useful for providing continuous application availability during maintenance. Not only can the workloads be easily moved to alternate systems but the processor activations and memory activations can be moved. Disaster recovery planning also is more manageable with the ability to move activations where and when they are needed.

Power Enterprise Pool configuration requirements

Two different types of Power Enterprise Pools are available:

• The IBM Power System 770, IBM Power System E870, IBM Power System E870C, and IBM Power System E880C Power Enterprise Pools
• The IBM Power System 780, IBM Power System 795, IBM Power System E880, IBM Power System E870C, and IBM Power System E880C Power Enterprise Pools

The Power 770 and 780 systems require a minimum of four static processor activations. The 9119-MHE and 9119-MME servers require a minimum of eight static processor activations. The Power 795 requires a minimum of 24 static processor activations. 50% of memory must be active for all systems, and a minimum of 25% of the active memory must be static memory. The Power 9119-MHE and 9119-MME servers have same minimum activations as the 9119-MHE and 9119-MME servers. However, the resources in these systems can go in any pool.

An HMC can manage multiple Power Enterprise Pools and can also manage systems that are not part of a Power Enterprise Pool. Systems can belong to only one Power enterprise pool at a time.

Master HMC and managing Hardware Management Consoles

The master HMC authorizes all Power enterprise pool change operations. It also performs all pool change operations for the servers that it manages. A managing HMC is an HMC that you designate to the master HMC of a pool as a managing HMC for the pool. A managing HMC can be directed by the master HMC to perform pool change operations for the servers that are not managed by the master HMC.

All managing HMCs must have an active network connection to the master HMC. The HMCs can communicate on either a public or a private network. The HMCs communicate by using the standard Resource Monitoring and Control (RMC) port 657. The master HMC communicates with all managing HMCs and all managing HMCs communicate with the master HMC. Managing HMCs do not communicate with each other, except when you are setting a managing HMC after the new master HMC when the current master HMC goes down.

Use static IP addresses for HMC-to-HMC communication.