Last Modified: May 29, 2024
Affected Product(s):
BIG-IP vCMP
Known Affected Versions:
14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1
Fixed In:
17.0.0, 16.1.2.2, 15.1.6.1, 14.1.4.6, 13.1.5
Opened: May 24, 2021 Severity: 3-Major
When trying to deploy a vCMP guest on an i11800 vCMP host using four or more cores while all of the other cores are in use, the following error message may be seen: err mcpd[<pid>]: 0107131f:3: Could not allocate vCMP guest (<guest_name>) because fragmented resources -------------------------------------------------- one more similar issue has raised for 8 guests allocation failure When trying to deploy a eight core guest on an i11800 vCMP host where four 2 cores are in use, the following error message may be seen: 0107131f:3: Could not allocate vCMP guest (guest-8cores-A) because fragmented resources
All of the available cores cannot be used.
-- VCMP provisioned and all or most cores are in use. -- Attempt to deploy a guest. This is more likely to occur with vCMP guests that use four or more cores.
You may be able to work around this by deploying the largest guests first, then any remaining 2-core guests. There is currently no other fix.
N/A