Bug ID 593597: iSession can't connect over default gateway pool

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: May 17, 2016

Severity: 3-Major

Symptoms

iSession can't make wocd (and data) connections if the required route defined as pool.

Impact

WOM cannot establish an iSession tunnel

Conditions

define WOM BIGIP peer in different subnets with router(s) in the middle. If the route from one BIG-IP to the other is defined as POOL the WOM daemons will be unable to connect.

Workaround

This issue can be mitigated if you can use a default gateway IP address instead of a default gateway pool.

Fix Information

iSessions can now be established when using a default gateway pool

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips