ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DCI1100E returned for LPARs with absolute capping

book

Article ID: 132776

calendar_today

Updated On:

Products

Dynamic Capacity Intelligence

Issue/Introduction

CA Dynamic Capacity Intelligence (DCI) doesn't recognize two LPARs with absolute capping as part of the Policy and lets them unmanaged.
These two lpars are defined in the policy as members of CG TEST:
20190514 110505 DCI1100E: WARNING: NEW SYSTEM 0AAA/LP01/SY01 IS NOT MANAGED AND WILL AFFECT GRP/CG CALCULATION
20190514 110505 DCI1100E: WARNING: NEW SYSTEM 0AAA/LP02/SY02 IS NOT MANAGED AND WILL AFFECT GRP/CG CALCULATION


They are set in the HMC as members of CG TEST. However, DCI treats both as members without assignment to CG:
DCI1101I: SYSTEM 0AAA/LP01/SY01 CHANGED CG FROM TEST TO DYNAMIC CAPPING FOR BOTH GROUPS IS STOPPED
DCI1101I: SYSTEM 0AAA/LP02/SY02 CHANGED CG FROM TEST TO DYNAMIC CAPPING FOR BOTH GROUPS IS STOPPED


As a result, both these LPARS are not managed by DCI.

Cause

According to the IBM WLM documentation, the set of an initial cap is not allowed for LPARs that are assigned to a Capacity Group. 
However, it seems to be possible to set an initial cap for LPARs within a Capacity Group, with the effect that the LPARs with an initial cap are internally no longer members of the Capacity Group, and therefore are no longer managed under the Capacity Group. 

In the SMF70 records of the LPARs, the Capacity Group Name field is still filled with the (now obsolete) CG Name. 
 

Environment

CA Dynamic Capacity Intelligence (DYCAPI) 1.5

Resolution

This is not a DCI bug but a policy change is required: remove the two LPARs from the policy CG group and define them as an own (DCI) Group under the CPC.