Bug ID 1215613: ConfigSync-IP changed to IPv6 address and it cannot be changed back to IPv4 address

Last Modified: Dec 20, 2023

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

Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3

Fixed In:
17.1.1, 15.1.10

Opened: Jan 03, 2023

Severity: 3-Major

Symptoms

In var/log/ltm following error log is available: 0107146f:3: Self-device config sync address cannot reference the non-existent Self IP (10.155.119.13); Create it in the /Common folder first.

Impact

Device is not able to configure the ConfigSync-IP for IPv4 once IPv6 is configured.

Conditions

- In High Availability (HA) system ConfigSync-IP is set to IPv6 management address. [root@00327474-bigip1:Standby:Disconnected] config # tmsh list cm device | grep -iE 'cm device|configsync-ip' cm device 00327474-bigip1.lucas { configsync-ip 10.155.119.12 cm device 00327474-bigip2.lucas { configsync-ip 2001:dead:beef::13 <<------- - Modifying the ConfigSync-IP to IPv4. tmsh modify cm device 00327474-bigip2.lucas configsync-ip 10.155.119.13

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips