MemCPUAllocator resource reports "Cannot allocate memory (4096 MB). Maximum limit reached."
Article ID: 100002740
Updated On:
Description
Error Message
VCS INFO V-16-10011-18504 (testLPAR) MemCPUAllocator:mymem:online:Current Memory = 1152, Minimum Memory = 1152, Maximum memory = 2176, Current Available System Memory = 29696
VCS WARNING V-16-10011-18505 (testLPAR) MemCPUAllocator:mymem:online:Cannot allocate memory (4096 MB). Maximum limit reached.
VCS ERROR V-16-10011-18508 (testLPAR) MemCPUAllocator:mymem:online:Memory allocation failed. Resource will not go Online
Cause
The LPAR has not been given sufficient memory allocation by the relevant HMC.
Reviewing the output of "lparstat -i", it is clear the LPAR hasn't been allocated sufficient memory for the VCS operation to succeed. In the output below, it is evident that the Maximum Memory is 2176MB, whereas the resource within VCS was trying to acquire 4096MB.
# lparstat -i|pg
Node Name : testLPAR
Partition Name : testLPAR
Partition Number : 2
Type : Dedicated-SMT
Mode : Capped
Entitled Capacity : 1.00
Partition Group-ID : 32770
Shared Pool ID : -
Online Virtual CPUs : 1
Maximum Virtual CPUs : 3
Minimum Virtual CPUs : 1
Online Memory : 2176 MB
Maximum Memory : 2176 MB
.
Resolution
In order for the LPAR to be allocated more memory, a change has to be made on the HMC managing the profile, in order to allocate further memory from the underlying system. Alternatively, the memory used by the service group has to be reduced to a suitable level such that it doesn't breach the maximum limit for the LPAR (as per "lparstat" output).
Applies To
Storage Foundation HA 5.1 for AIX and LPAR/HMC configuration
Issue/Introduction
