Bug ID 2284409: No automatic reassignment of freed IPs to failed gateways

Last Modified: Sep 02, 2026

Affected Product(s):
BIG_IP_NEXT(BNK) BNK(all modules)

Known Affected Versions:
2.3.0, 2.3.1, 2.3.2

Opened: Apr 18, 2026

Severity: 2-Critical

Symptoms

When the IP pool is exhausted, new Gateway resources fail to obtain an IP address. When a Gateway is deleted and its IPs are freed, the IPs are not automatically reassigned to Gateways that previously failed due to IP exhaustion.

Impact

- Gateways that failed due to IP exhaustion remain failed. - IP allocation isn’t automatically retried for affected Gateways. - Manual intervention is required to recover.

Conditions

Occurs when - The IP pool is fully exhausted. - Multiple Gateway resources fail due to lack of available IPs. - An existing Gateway (with a successfully allocated IP) is deleted, freeing an IP.

Workaround

To allocate an IP to a Gateway that failed due to IP exhaustion: 1. Delete the affected Gateway resource. 2. Recreate the Gateway resource. This triggers a new IP allocation attempt, allowing the system to assign any available (freed) IP.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips