Forum Discussion
Radius Persistence iRule error (bad field specifier)
Maybe you could use another Radius persisting iRule? I've been using the following:
- add an radius service profile to the virtual server.
- create an universal persistence profile and use the following iRule:
when CLIENT_ACCEPTED {
set framed_ip [RADIUS::avp 8 ip4]
set calling_station_id [RADIUS::avp 31 "string"]
persist uie "$calling_station_id:$framed_ip"
}
- Add the universal persistence profile to the virtual server.
- adammMay 29, 2019Altostratus
I likely can. I was using a canned irule recommended by Cisco for load balancing ISE PSNs for MAB authentication. Since it's recommended, I was curious as to why I was having so many issues with it. It's also a good chance to learn.
I will troubleshoot this a bit more for learning if nothing else and may implement your recommendation in the end. Thanks much for your help.
- ewwOct 15, 2020Nimbostratus
Hi Niels van Sluis
We are struggling with the iRules on LTM 15.5. Once we use iRules we get errors on ISE. Is there anything special that needs to be done to enable the iRules to work well?
Recent Discussions
Related Content
* 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