Bug ID 860181: After sync failure due to lack of local self-IP on the peer, adding in the self-IP does not resolve the sync error

Last Modified: Apr 29, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 16.0.0,, 16.0.1,,

Opened: Dec 11, 2019

Severity: 3-Major


If you have BIG-IPs in a Device Service Cluster, and you attempt to sync a new floating self-IP over to a standby on a VLAN that the standby does not currently have a non-floating self-IP on, you will get an error and the sync will fail. This is the correct behavior. The issue, though, is that if you subsequently create a non-floating self-IP on the standby in order to rectify this issue, the sync will still fail.


You are unable to sync BIG-IPs. Both devices will be out of sync and you will see an error displayed: 01070355:3: Self IP <address> is declared as a floating address but there is no non-floating address defined for this network Even after you add a non-floating self-IP on the affected device, a subsequent config sync does not fix the error.


-- BIG-IPs configured in a Device Service Cluster. -- Device group is configured to use Automatic Sync or Manual with Incremental sync. -- Attempting to sync a floating self-IP to a system that does not have a non-floating self-IP on the same VLAN.


If you make any other configuration change that generates a config sync, this will correct itself after the other device has added a non-floating Self-IP. Otherwise, this can be corrected by doing a full config sync, and can be done via the GUI or via tmsh. In the GUI, change the Sync Type for the device group to Manual with Full Sync, and then do a config sync. In tmsh, the command is: run cm config-sync force-full-load-push to-group <affected_device_group>

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips