Bug ID 664535: Diameter failure: load balancing fails when all pool members use same IP Address

Last Modified: Sep 13, 2023

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3

Opened: May 12, 2017

Severity: 2-Critical

Symptoms

Case1: Run 2 Servers with same IP but different ports. Send 10 request from 1 client. Result: All 10 requests from client are delivered to 1 server. Same result when use-local-connection is disabled. Case2: Run 2 Servers with same IP but different ports but this time use MR::message route iRule command to route messages between hosts. Send 10 request from 1 client. Result: All 10 requests from client are delivered to 1 server.

Impact

All the requests from the same client are delivered to 1 server only.

Conditions

Load balancing scenario with single client and two pool members. The servers use same IP, different ports.

Workaround

Use different IP address in the pool member. Or use different IP address as the client request.

Fix Information

Load balancing scenario with single client and two pool members now completes successfully even when all pool members use same IP Address.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips