Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP APM
Known Affected Versions:
12.1.2, 12.1.2 HF1, 12.1.2 HF2, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Fixed In:
14.0.0
Opened: Sep 08, 2017 Severity: 3-Major
Config objects such as RADIUS server in APM or traffic class in LTM that contain the IP address field, when left empty and created in a partition that is associated with a route domain, the value is auto-changed to '::0.0.0.0' after save.
The value in the database does not change. This is a cosmetic issue only and represents on functional issue.
Configuring APM RADIUS authentication with an empty nas-ip-address.
Use tmsh to see APM RADIUS authentication nas-ip-address using the following command: tmsh list apm aaa radius <name>
Empty APM RADIUS authentication nas-ip-address is no longer automatically filled.