Last Modified: Feb 21, 2019
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 14.0.0, 22.214.171.124, 126.96.36.199
14.1.0, 188.8.131.52, 184.108.40.206, 12.1.4
Opened: May 17, 2018
When a BIG-IP iSeries i5800, i7800, or i10800 device is configured as a vCMP host and at least one vCMP guest is running (or ever ran), TMM traffic to the vCMP host may fail. Note: Management port traffic to/from the device is unaffected. Note: TMM traffic to/from the vCMP guests running on the device is unaffected. This issue affects only the vCMP host. The most visible symptom is that TMM on the vCMP host fails to answer ARP requests that it receives for its own Self-IP addresses.
Inability to communicate to/from the vCMP host via its Self-IP addresses.
This issue occurs when all of the following conditions apply: - BIG-IP iSeries i5800, i7800, or i10800 device in vCMP host mode. - At least one vCMP guest is deployed or was deployed, at some point.
Ensure that the host is running a compatible version of BIG-IP. For more information on supported host/guest versions, see K14088: vCMP host and compatible guest version matrix, available at https://support.f5.com/csp/article/K14088
The vCMP host continues to handle traffic correctly once a guest is started.