Bug ID 564537: Admin must not change the port for Pool member automatically created by APM

Last Modified: Jul 12, 2023

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

Fixed In:
12.1.0

Opened: Dec 23, 2015

Severity: 2-Critical

Symptoms

During the creation of AAA radius server, when the selection of mode is Radius mode both (ACCT and AUTH) and the user uses POOL, a pool member is created with 0 (Any - as the port number). This must not be changed by the Admin manually. This is true for the AD server pool member port as well.

Impact

May cause in-correct behavior.

Conditions

If the AAA radius server is created with Radius mode BOTH in case of a POOL, the pool member is created with (0) '- Any port' as there are more than one ports involved. if AAA RADIUS Server is configured for "auth" mode, then create layered VS/pool with port derived from AAA RADIUS server configuration if AAA RADIUS Server is configured for "acct" mode, then create layered VS/pool with port derived from AAA RADIUS server configuration

Workaround

Going back to the Radius server page and clicking on the Update will restore the pool member back to 0 when the Radius mode BOTH is selected.

Fix Information

The RADIUS server setting must be changed only from the APM RADIUS server config page. If AAA RADIUS Server is configured for "both" mode, then create layered virtual server/pool with * (any) port.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips