EP 2.0: Settings

To manage the pool and threshold settings, click the Settings () icon.

Delete Pool

Click Delete Pool to delete a pool. Once the action is confirmed, it cannot be undone. CMC contacts Entitled Systems Support (ESS) to get the pool termination CoD code for each system in the pool. A managing HMC for each system retrieves the CoD code from CMC and enters it into the system. When the CoD code is successfully entered into the system, the system is removed from the pool. The system's base resources are permanently activated on the system, and the remaining processor and memory resources on the system are activated with Trial CoD for 30 days. After all systems are removed from the pool, the pool is permanently deleted. 

Pool Details

The following pool details are displayed:

• Pool ID. This is the pool ID provided by Entitled Systems Support.  This setting cannot be changed.
• Pool Type. This is the pool type you chose when you created the pool.  This setting cannot be changed.
• Dedicated Processor Partitions Allowed. Pools can have dedicated processor partitions based on the selection made during pool creation time. The possible values are Yes and No. This setting cannot be changed.
• Pool Name. This is the name you chose when you created the pool. You can change this name.
• Description. This is the description you chose when you created the pool. You can change this description.

Partition Core Usage %

Select whether shared processor partition core usage percentages and thresholds are based on entitled cores or virtual processors.  Dedicated processor partition core usage percentages and thresholds are always based on entitled cores, even when Virtual Processors is selected here. Partition core usage percentages are shown on the Inventory and Core Usage pages.

Thresholds

You can configure system and partition thresholds, budget, and remaining credit balance thresholds. When a threshold is reached, a notification is generated. Based on what you specify in Notification Settings, the threshold notifications are displayed in the application, and also sent by email and text message.

Pool Thresholds

You can specify the pool thresholds for hardware, LPP[SJ1] [PA2] , and software base core usage. The LPP toggle switch is available only for pools in which there is at least one partition with a reserved PowerHA tag. If a pool has zero base cores of a resource, the pool threshold for that resource is ignored. By default, the pool thresholds are set at 70%, but are disabled.

A separate notification is generated for each resource type in the pool. For example, if the thresholds for hardware and LPP are reached, one notification will be generated for hardware and one for LPP. However, if for the same resource type, the threshold is reached for different resources, a single notification is generated. For example, if AIX and Linux RedHat usage each reaches the software threshold at the same time, a single notification is generated because both resources belong to the software resource type. If AIX and Any O/S usage each reaches the respective pool thresholds at the same time, separate notifications are generated; one notification for software for the AIX usage and one for hardware for the Any O/S usage.

If the pool contains different PowerHA resource type base, a notification is triggered only when the usage of the highest PowerHA resource type in the pool reaches the LPP threshold since lower PowerHA resource types can share higher PowerHA base and metering of PowerHA resources does not start until the highest PowerHA base is all used. This notification contains the usage details of all the PowerHA resource types that are present in the pool. For example, if a pool contains PowerHA AIX Standard and PowerHA AIX Enterprise, a notification is triggered only when the PowerHA AIX Enterprise usage reaches the LPP threshold. The notification includes usage of PowerHA AIX Standard and PowerHA AIX Enterprise.

Similarly, if a pool contains different tiers of IBM i base, a notification is triggered only when the usage of the highest tier in the pool reaches the software threshold since lower IBM i tiers can share higher IBM i tier base and metering of IBM i does not start until the highest IBM i tier base is all used. This notification contains the usage details of all the IBM i tiers that are present in the pool. For example, if a pool contains IBM i P10 and IBM i P20, the notification is triggered only when the usage of IBM i P20 reaches the software threshold. The notification includes usage of IBM i P10 and P20.

For hardware notifications, if a pool contains Any O/S base, a notification is triggered only when AnyO/S usage reaches the hardware threshold since Linux/VIOS usage can share Any O/S base and metering of hardware cores does not start until the Any O/S base is all used. The notification includes the usage of Any O/S and Linux/VIOS.

Pool threshold notifications for a resource are not repeated for the same resource unless at least 60 minutes have elapsed since the last notification.

Enabled pool thresholds are visible on the Inventory page when capacity usage reaches the specified thresholds.  A red dot is shown next to the pool base resources that have reached their thresholds.

System and Partition Thresholds

If more than one system reaches the same system system threshold at the same time, a single notification is generated. Likewise, if more than one partition reaches the partition threshold at the same time, a single notification is generated. Another notification is not generated for the same system or partition and the same threshold for about 60 minutes.

Enabled system and partition thresholds are visible on the Inventory, Core Usage, and Memory Usage pages when capacity usage reaches the specified thresholds. Each capacity usage value that has reached the specified threshold appears in a red box.

Other Thresholds

Multiple budget and remaining credit balance thresholds can be added and enabled. Notifications are always generated when a monthly budget is reached, or when the remaining credit balance reaches zero, regardless of if they are configured. The remaining credit balance threshold is not shown or checked for pools with monthly billing.

Note: Budget thresholds and notifications can still be used in a pool that allows dedicated processor partitions, even though there isn’t any budget enforcement.

To remove all custom thresholds and reset all thresholds to their default values , click Restore Threshold Defaults.

Usage Statement Email

To send a monthly credit usage statement for the pool to the listed email addresses, enable this option. You can add or remove email addresses from this list at any time. Separate multiple email addresses with a comma.

The credit usage statement is sent on the first day of each month and contains the credit usage for the previous month, in the following format:

Enterprise Pool

Metered Resource	Credits	Minutes
Any O/S Cores
Linux/VIOS Cores
AIX Software
IBM i Software - P10
IBM i Software - P20
IBM i Software - P30
RHEL Software
RHEL CoreOS Software
SLES Software
PowerHA AIX Standard
PowerHA AIX Enterprise
PowerHA IBM i Small
PowerHA IBM i Medium
Memory

Total credits

Displays the remaining credit balance as of last date of previous month.

Note: The amount shown here may differ from the invoiced amount due to a different usage period for invoicing. For more information about the usage orders used for invoicing, visit the Entitled Systems Support website.

Parent topic: Power Enterprise Pools 2.0 with Utility Capacity