Last Modified: Jan 20, 2023
See more info
Known Affected Versions:
14.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 14.1.2, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.3, 22.214.171.124, 14.1.4, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 14.1.5, 126.96.36.199, 188.8.131.52, 184.108.40.206, 15.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 15.1.1, 15.1.2, 184.108.40.206, 15.1.3, 220.127.116.11, 15.1.4, 18.104.22.168, 15.1.5, 22.214.171.124, 15.1.6, 126.96.36.199, 15.1.7, 15.1.8, 188.8.131.52, 16.1.0, 16.1.1, 16.1.2, 184.108.40.206, 220.127.116.11, 16.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 17.0.0, 188.8.131.52, 184.108.40.206
Opened: Jul 02, 2022
After performing a specific type of software installation, the unit returns on-line without the management port's default gateway.
On Virtual Edition systems, this issue coupled with the removal of autolasthop from the management port means you will not be able to connect to the BIG-IP system's management port from non-directly connected clients after the installation. On all systems, this issue means the BIG-IP system will not be able to initiate connections to non-directly connected systems over the management port after the installation. Note: If the system is configured for dual-stack (IPv4 and IPv6) this issue can affect either (or both) stack.
-- A software installation that does not carry forward the entirety of the BIG-IP system's configuration is performed. For example, this is achieved by running "image2disk --format=volumes <...>", or by using the live-install subsystem after disabling the liveinstall.saveconfig and liveinstall.moveconfig db keys. This type of installation, however, does carry forward the management port's configuration (IP address, subnet mask, and default gateway). -- In addition to the default gateway, the management port is configured with additional static routes (for example, to a log server, dns server, etc.). -- When mcpd is queried for the management routes, the default gateway is not the first entry in mcpd's reply (this is something outside of your control that entirely depends on the name of the objects and how the config was loaded).
After the issue has occurred, you can connect to the affected BIG-IP system by means of serial console or video console and apply the default gateway again. If you are trying to prevent this issue, you can remove all management routes except the default one before performing this type of installation.