Forum Discussion
I believe the RADIUS commands are no longer allowed in the CLIENT_ACCEPTED events.
We solved the issue by doing priority groups to ensure that everything went to the same server.
Hi, I'm about to try to activate a similar configuration as well.
We're passing from Citrix Netscaler to F5 LTM and I'm using radius profile with persistence attribute 31, just like I had configured in netscaler.
Has anyone tested this before? Does it work as expected?
I have to mention we tried to go-live once already but VS seemed to receive no traffic from switches. The switches passed from seeing radius server from "DEAD" to "ACTIVE", but still all I could see on the loadbalancer with a tcpdump instance listening on udp port 1812 was F5 monitor traffic.
I've suspected the firewall *might* not have updated ARP entry for VS IP (we used the same addresses) so ethernet packets were crafted with bad destination mac, and this will be the first thing I'll check next time we try, but I was also wondering if anything on BIGIP configuration might be misfunctioning.