Forum Discussion
Ed3
Mar 04, 2022Nimbostratus
Updated iRule for radius called-station-id attribute 31 (persistence)
Hello Folks, Is there an updated iRule for radius called-station-id attribute 31 (persistence) that is available ? There was one posted several years ago and being new to iRules, it doesn't work wit...
CA_Valli
Mar 07, 2022MVP
Hello Ed3, I've configured radius persistence on a customer last year without need for an iRule.
There's persist option available in RADIUS type traffic profile.
Other than that, you'll need an universal persistence profile that enables cross-service persistence (used for accounting/authentication persistence on same server).
ltm persistence universal /Common/radius_xsvc {
app-service none
defaults-from /Common/universal
match-across-services enabled
timeout 300
}
ltm profile radius /Common/radiusLB_31 {
app-service none
clients none
defaults-from /Common/radiusLB
persist-avp 31
}
Apply both profiles in both your VS's for auth/acc.
Also, check this link: https://support.f5.com/csp/article/K52316490
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects