OPERATIONAL DEFECT DATABASE
...
...
When you load a UCS file using the platform-migrate parameter, the mgmt-dhcp value (enabled, disabled, or unset) will overwrite the value on the destination. Depending on the effect, this could change the destination's management IP and default management route. If the UCS does not have mgmt-dhcp explicitly written out, note that its value is treated as the default for the local system, which varies by the type of system. On Virtual Edition (VE) platforms, the default is to enable DHCP. On all other platforms, the default is to disable DHCP.
Changing the mgmt-dhcp value on the destination can result in management changing from statically configured to DHCP or DHCP to statically configured. This can result in loss of management access to the device, requiring in-band or console access.
This occurs when loading a UCS using the platform-migrate parameter: tmsh load sys ucs <ucs_file_from_another_system> platform-migrate
There are a few ways to avoid this issue: 1. Specify the "keep-current-management-ip" parameter to the "load sys ucs" command, for instance: tmsh load sys ucs <ucs_file_from_another_system> platform-migrate keep-current-management-ip Note: The "keep-current-management-ip" parameter is undocumented and will not appear in context help or tab completion. 2. If you want to reset the target device to use a static IP, run the following commands after loading the UCS with the platform-migrate command: tmsh modify sys global-settings mgmt-dhcp disabled tmsh create sys management-ip <ip>/<mask> tmsh delete sys management-route default tmsh create sys management-route default gateway <ip>
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
