Bug ID 1121633: Management route lost after reboot when default route is named something other than "default"

Last Modified: Apr 28, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 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

Opened: Jun 24, 2022

Severity: 3-Major

Symptoms

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.

Impact

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.

Conditions

-- 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). -- network default route is named something other than "default". -- The instance is rebooted.

Workaround

Use either of the following workarounds: -- Delete the route completely and reinstall the route. -- Restart mcpd: bigstart restart mcpd

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips