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

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
10.2.4, 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.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0

Opened: Oct 20, 2014
Severity: 3-Major
Related AskF5 Article:
K16152

Symptoms

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

Impact

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.

Conditions

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

Workaround

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