Bug ID 427249: For a catch-all traffic virtual server without a default pool, the final flow in w-steering might reset

Last Modified: Apr 28, 2025

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

Known Affected Versions:
11.4.0

Fixed In:
11.5.0

Opened: Aug 06, 2013

Severity: 3-Major

Symptoms

If you are using a SNAT disabled catch-all virtual server that has no default pool, the server-side connection might reset.

Impact

Connection is reset.

Conditions

This occurs with the following configurations: 1- Catch all virtual (destination network 0.0.0.0/0:0). 2- SNAT disabled. 3- No default pool. Also this happens only before the classification cache is trained, which requires at least two flows.

Workaround

There are many workarounds: 1- Train srDB by sending two or more flows, and the third flow will not see a reset. 2- Use a virtual server with SNAT enabled (or automap). 3- Add a default pool to the virtual server.

Fix Information

Server-side connection is now correctly set when using a SNAT disabled catch-all virtual server that has no default pool.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips