Last Modified: Mar 17, 2021
See more info
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, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 11.6.4, 11.6.5, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4
Opened: Oct 20, 2014
Related AskF5 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
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.