Bug ID 709274: RADIUS Accounting requests egress on different Self IP addresses than they did pre-v13.1.0

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7

Fixed In:
14.0.0, 13.1.0.8

Opened: Mar 07, 2018
Severity: 3-Major

Symptoms

RADIUS Accounting requests egress different self IP addresses. * START accounting message egresses floating self IP addresses. * STOP accounting message egresses local self IP addresses. Some RADIUS messages will come from floating IP addresses, some from self IP addresses. The RADIUS server should be configured to accept all self- and floating-IP addresses of all the devices in the high availability (HA) group, to ensure all messages are received.

Impact

Causes RADIUS server to be unable to reconcile accounting messages.

Conditions

RADIUS server configured with pool option.

Workaround

You can reconcile accounting messages by tracking them through the Acct-Session-Id in RADIUS AVP's message, which is the same for the corresponding START and STOP messages to uniquely identify the session.

Fix Information

RADIUS START and STOP messages now egress the same interface.

Behavior Change