Bug ID 485432: Notice when changing management IP when management routes are configured.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
10.2.4, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: Oct 20, 2014

Severity: 3-Major

Related Article: K16152


When you change the management port's subnet, existing management routes that now have topologically unreachable gateways trigger log messages in /var/log/ltm.


Traffic using management routes, such as NTP, SNMP, SMTP, and logging, might not be deliverable from the BIG-IP system after reconfiguring the mgmt port, if the routes' gateways are not updated.


Management routes exist whose gateways are not on a local subnet, after the mgmt port takes on a new address.


Update management routes' gateways so they remain within the local subnet of the mgmt port address

Fix Information

If the management address of a BIG-IP is changed but management routes are configured with gateways in the old management address's subnet, the system generates a number of messages to acknowledge the broken configuration. This alerts you to the need to modify the management routes' gateways.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips