Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP vCMP
Known Affected Versions:
11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Fixed In:
11.5.0, 11.4.1 HF9
Opened: Jul 22, 2013
Severity: 3-Major
Related Article:
K14665
Multiple vcmp instances may use the same mac addresses when running fastL4 traffic.
This issue can cause traffic disruption, traffic being directed to the wrong vcmp instance, and incorrect learning on upstream devices.
This issue can be triggered by loading a configuration, ucs, or scf containing vcmp objects in the provisioned or deployed state while the running system is not provisioned for vcmp. It may also be triggered during a relicensing event if the system has vcmp guests provisioned or deployed and is restarted prior to applying an updated license.
Set all vcmp guests to the configured state. After all guests are down, they may be redeployed as desired.
Loading a configuration with vcmp guests no longer causes incorrect guest settings.
