Bug ID 470207: Copying configuration leads to two mgmt IP addresses

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 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.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.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.4

Fixed In:

Opened: Jul 03, 2014
Severity: 3-Major
Related AskF5 Article:


Copying configuration leads to two mgmt IP addresses.


When that configuration is rolled forward to a non-active volume (using 'cpcfg' utility or the GUI), and the newly upgraded volume is booted up, there are two mgmt IP addresses. An appliance has two management IP addresses, the old one (the IP address that was previously on the volume) and the new one (IP address from the configuration that was copied from). On a chassis, the primary slot has the cluster mgmt IP but does not have the mgmt IP for the slot. Secondary slots have both the old IP as well as the new one.


This issue can occur when the BIG-IP system has two boot volumes with the same static mgmt IP address configured, and there is a change to the mgmt IP on the active volume.


Restart the network: service network restart. Restart might result in traffic disruption.

Fix Information

When the BIG-IP system adds a new IP address on the mgmt interface, the former mgmt IP address is deleted. This prevents the issue of having two mgmt IP addresses.

Behavior Change