Bug ID 744740: After upgrade, dhclient overwrites configured hostname, even when 'sys management-dhcp' does not contain the 'host-name' in the request-options.

Last Modified: Sep 14, 2023

Affected Product(s):
BIG-IP Install/Upgrade, LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 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,,,,,

Fixed In:

Opened: Sep 21, 2018

Severity: 3-Major


The configured hostname is overwritten by dhclient after upgrade.


Incorrect hostname assigned to the BIG-IP system.


-- DHCP enabled. -- Custom hostname configured using the procedure described in K45728203: AWS generates the BIG-IP VE instance host name to include the host name's private IP address :: https://support.f5.com/csp/article/K45728203, instead of using the one provided by the DHCP server.


Change the DHCP settings, and issue the following command to correct the name without losing connectivity to management: # tmsh modify sys global-settings mgmt-dhcp disabled; tmsh modify sys global-settings mgmt-dhcp enabled

Fix Information

Disable and reenable dhclient to fix the dhclient overwritten hostname after upgrade when 'sys management-dhcp' does not contain the 'host-name' in the request-options.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips