Last Modified: Oct 17, 2023
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0
Opened: Sep 19, 2016 Severity: 5-Cosmetic
On a BIG-IP provisioned with LTM only, the radius profile called radiusLB-subscriber-aware displays inconsistent information between tmsh and configuration utility
On a device that does not have PEM licensed: root@(v12)(cfg-sync Changes Pending)(Active)(/Common)(tmos)# list ltm profile radius radiusLB-subscriber-aware ltm profile radius radiusLB-subscriber-aware { app-service none defaults-from radiusLB } However, viewing the profile in the configuration utility Local Traffic :: Profiles : Services : RADIUS : radiusLB-subscriber-aware Settings field Custom checkbox Persist Attribute disabled Subscriber Discovery enabled Client Spec disabled Protocol Profile(_sys_radius_proto_imsi) enabled On a device which does not PEM licensed, the Protocol profile should be set to None but shows as enabled.
This occurs when looking at the radiusLB-subscriber-aware profile in both tmsh and the GUI.
None
None