Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP Install/Upgrade, vCMP
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 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, 11.5.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 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
Opened: May 30, 2014 Severity: 3-Major Related Article:
K15801
The vCMP guest's cluster IP address gets reset to the default IP of 192.168.1.246 when upgrading a guest that has no 'management-ip' attribute set in the host.
The guest's cluster IP address gets reset to the default IP of 192.168.1.246 when booting into a newly installed build. In most cases, the change in IP address does not matter, since a guest in isolated network mode has no need for a non-default cluster IP address. However, devices in an HA configuration, even if the HA happens over self-IP addresses, require unique cluster IP addresses.
This occurs only when the vCMP guest has no 'management-ip' attribute set on the host and the guest is upgraded.
Set the guest's 'management-ip' attribute in the host. This prevents a guest's management IP from being reset when the guest is upgraded. Alternatively, after the guest has been upgraded and booted into the new version, set its cluster IP address to what it was before the upgrade.
None