When you share Mobile Capacity on Demand (CoD) resources
among servers in a
Power® Enterprise Pool
,
the pool must be in compliance with your CoD licensing agreements.
The resource entitlements for the pool are procured through
your CoD licenses, which include a grace period for overuse of these
resources. The resource entitlements for the pool must synchronize
with the actual usage of those resources. You can temporarily overuse
the Mobile CoD pool resources. However, the grace period in your licenses
restricts this overuse. When resources are in use beyond the grace
period, those resources are overdue and the server is out of compliance
with the CoD license. Compliance policies for the
Power Enterprise Pool
are based on
your CoD licenses and these policies enforce resource availability
and usage restrictions for the pool.
The Mobile CoD resource
compliance of the servers in the pool determines the compliance state
of the pool itself. A server is in compliance if the server does not
have any unreturned Mobile CoD resources.
A
Power Enterprise Pool
can have one
of the following four compliance states:
-
In compliance
-
None of the servers in the pool have any unreturned Mobile CoD
resources.
-
Approaching out of compliance (within server grace period)
-
At least one server in the pool has Mobile CoD resources that
are unreturned, and the server grace period for those resources is
unexpired. None of the servers in the pool have Mobile CoD resources
that are unreturned and overdue.
-
Out of compliance (within pool grace period)
-
At least one server in the pool has overdue, unreturned Mobile
CoD resources and the pool grace period is unexpired.
-
Out of compliance
-
At least one server in the pool has overdue, unreturned Mobile
CoD resources and the pool grace period is expired.
A Mobile CoD resource becomes an unreturned
resource under the following conditions:
-
You remove the Mobile CoD resource from a server, but the server
cannot reclaim the resource because that resource is still in use.
For example, the resource is assigned to one or more partitions. You
must remove the partition assignments to enable the server to reclaim
the resource.
-
You remove a Mobile CoD resource from a server that is not connected
to the master
Hardware Management Console
(
HMC
) of the pool.
When Mobile CoD resources that are removed from a server
become unreturned, a grace period timer starts for the unreturned
resources on that server. There is a separate grace period timer for
unreturned Mobile CoD processors and for unreturned Mobile CoD memory
on each server.
Before a server grace period expires, you must
release the unreturned Mobile CoD resources and make them available
for the server to reclaim. If a resource remains unreturned after
the end of the grace period, the pool is out of compliance. When the
pool moves to the out of compliance state, a new grace period timer
starts for the pool itself. There is only one grace period timer for
the pool. If any servers have overdue Mobile CoD resources when the
pool grace period expires, add operations for Mobile CoD resources
are restricted to servers with unreturned Mobile CoD resources. This
restriction is enforced until there are no servers in the pool with
overdue unreturned Mobile CoD resources.
When a server in a
pool is out of compliance, or the pool is out of compliance, console
messages are displayed on the
HMC
s that manage the pool.
To
view compliance information for a
Power Enterprise Pool
, complete the
following steps:
-
From the master
HMC
for
the pool, select
Systems Management > Power Enterprise
Pools
.
-
In the left navigation pane, select the pool name and then select
Compliance
Information
.
Resolving compliance issues
To avoid compliance
issues, ensure that Mobile CoD resources are released on a server
before you remove the resources from that server. Also, do not remove
Mobile CoD resources from a server that is not connected to the master
HMC
for the pool.
If
you want to overuse your Mobile CoD resources when migrating partitions,
ensure that all Mobile CoD resources removed from the source server
are released and reclaimed by the source server as soon as the migration
completes. If the migration fails, immediately remove the Mobile CoD
resources added to the destination system and add them back to the
source system.
You can resolve unreturned Mobile CoD resources
in any of the following ways:
-
Migrate a partition to another server. After the partition migrates
successfully, any resources that are assigned to the partition on
the source server are reclaimed automatically.
-
Remove resources from a running partition by using the appropriate
dynamic logical partition (DLPAR) task.
-
Remove resources from a shutdown partition.
-
Delete a partition to release resources that are assigned to that
partition.
-
Activate Capacity Upgrade on Demand (CUoD), On/Off CoD, or Trial
CoD resources.
-
Add Mobile CoD resources to the server.
Note:
When a server is powered off, any unreturned Mobile CoD
resources are reclaimed automatically by the master
HMC
for the pool.
If
the server is not connected to the master
HMC
for the pool, you must
establish a connection from the master
HMC
to that server. After
you reestablish the connection, if any unreturned Mobile CoD resources
remain on the server, take one of the previously stated actions to
release them. If you cannot reestablish this connection, you can add
Mobile CoD resources to the server to resolve the unreturned resources.