Bug ID 739118: Manually modifying a self IP address in bigip_base.conf file and reloading the configuration results in routing misconfiguration

Last Modified: Sep 16, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,, 15.0.0, 15.0.1,,,,

Opened: Aug 02, 2018
Severity: 3-Major


Changing existing self IP addresses in bigip_base.conf file directly. After uploading the changed configuration file, BIG-IP routing service provides out of date Self IP route information to dependent services.


Different services have different route information: -- tmsh table - has the old route. -- Dynamic routing - hHas the old and new routes. -- Kernel table - has the new route.


- Self IP address is configured on the BIG-IP system. - Manually change the IP address of a self IP in bigip_base.conf file. - Load changed configuration via tmsh.


There are two workarounds, preventive and corrective. Preventive: Do not manually change self IP addresses in bigip_base.conf file. It is not recommended way to add/change BIG-IP configuration. Use GUI or tmsh instead. Corrective: If changed configuration is uploaded. In GUI or tmsh, delete changed self IP address, and then create a self IP address with old IP address and delete it as well. Now, all affected routes are removed.

Fix Information


Behavior Change