Last Modified: Jul 24, 2024
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3
Opened: Jun 24, 2022 Severity: 3-Major
When the default route name is changed to something other than "default", this results in the management route being lost after reboot, leading to no access to BIG-IP systems via the management address.
After rebooting, the default route via the management interface no longer exists in the routing table. BIG-IP administrators are unable to connect to BIG-IP Virtual Edition via the management address.
-- 2NIC BIG-IP Virtual Edition template deployed in GCP (see https://github.com/F5Networks/f5-google-gdm-templates/tree/v3.0.3/supported/standalone/2nic/existing-stack/byol) OR (https://github.com/F5Networks/f5-google-gdm-templates-v2/tree/main/examples/modules/bigip-standalone). -- network default route is named something other than "default". -- The instance is rebooted.
Use either of the following workarounds: -- Delete the route completely and reinstall the route. -- Restart mcpd: bigstart restart mcpd
None