Last Modified: Oct 16, 2023
Affected Product(s):
BIG-IP vCMP
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.6.2 HF1, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0, 11.6.0 HF5, 11.5.1 HF6
Opened: Oct 09, 2014 Severity: 3-Major Related Article:
K15790
Intermittent traffic disruptions such as unexpected resets and drops may occur as the result of MAC address conflicts between vCMP guests on an affected hypervisor and/or conflict with other F5 devices with adjacent MAC address ranges.
Intermittent traffic disruptions such as unexpected resets and drops.
MCPD has restarted on a vCMP hypervisor, and vCMP guest instances with more than 2 VLANs are deployed after the MCPD restart.
1. Restart vCMPD on the hypervisor. 2. Re-deploy the vCMP Guest by setting it to "Configured", then "Deployed" again. Note, you need to set to "Configured", not "Provisioned".
MAC address conflicts no longer occur between vCMP guests when the vCMP hypervisor is running a fixed version. If a vCMP guest running a fixed version detects that the hypervisor has provided an invalid set of MAC addresses, the guest will log an error similar to err chmand[28121]: 012a0003:3: unexpected init failure : VcmpPlatform: MAC pool size from hypervisor is zero crit chmand[28121]: 012a0002:2: critical platform initialize failure. exiting... and not start.