Bug ID 1585309: Server-Side traffic flows using a default VRF even though pool is configured in a non-default VRF

Last Modified: Oct 19, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) LTM(all modules)

Known Affected Versions:
20.2.1

Opened: May 09, 2024

Severity: 2-Critical

Symptoms

Traffic flows when a default VRF is configured and a pool is configured in a non-default VRF without a route in non-default VRF.

Impact

Traffic continues to work when pool is configured in non-default VRF, but there is no route in non-default VRF.

Conditions

- Default VRF is configured - Pool is configured in non-default VRF - Route to pool exists in default VRF, but not in non-default VRF.

Workaround

For network isolation, do not configure a default VRF. Use all non-default VRFs in the configuration.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips