RADIUS persistence

As there is no timeout parameter in the profile I would guess a kind of hashing will be applied.

To be on the safe side you can cross check on your own by monitoring the persistence table:

watch -d tmsh show ltm persist persist-records

Or the verbose version:

watch -d tmsh show ltm persist persist-records all-properties

Sorry for not beeing able to provide a better answer.

Hi,

 

I'm working on something similar to this one. At least on version 11.5.2, this is based on Universal persistence and not on hash, although configured in the RADIUS Profile.

 

In Profiles -> Services -> Radius -> CustomRadiusProfile, configure the following: Persist Attribute = 1 (i.e. AVP User Name) Susbcriber Aware = Enabled Subscriber ID Type = User Name

 

Need to configure a universal persistence profile to define: - Match accorss services, virtual servers and pools - Manage persistence timeout

 

Assign both profiles to the Radius Virtual Server, generate traffic, and looking at persistence records:

 

root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos) show ltm persistence persist-records Sys::Persistent Connections universal f5user1 10.128.10.101:1812 10.128.20.21:1812 (tmm: 1) Total records returned: 1 root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos)

 

WAIT THE TIME DEFINED TIMEOUT OF THE UNIVERSAL PERSISTENCE PROFILE

root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos) show ltm persistence persist-records Sys::Persistent Connections Total records returned: 0 root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos)

 

Cheers João

 

Hi,

 

I'm working on something similar to this one. At least on version 11.5.2, this is based on Universal persistence and not on hash, although configured in the RADIUS Profile.

 

In Profiles -> Services -> Radius -> CustomRadiusProfile, configure the following: Persist Attribute = 1 (i.e. AVP User Name) Susbcriber Aware = Enabled Subscriber ID Type = User Name

 

Need to configure a universal persistence profile to define: - Match accorss services, virtual servers and pools - Manage persistence timeout

 

Assign both profiles to the Radius Virtual Server, generate traffic, and looking at persistence records:

 

root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos) show ltm persistence persist-records Sys::Persistent Connections universal f5user1 10.128.10.101:1812 10.128.20.21:1812 (tmm: 1) Total records returned: 1 root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos)

 

*** WAIT THE TIME DEFINED TIMEOUT OF THE UNIVERSAL PERSISTENCE PROFILE ***

 

root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos) show ltm persistence persist-records Sys::Persistent Connections Total records returned: 0 root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos)

 

Cheers João