Forum Discussion
Is there a way for a single request to be received by all pool members
Hi Ferdz;
Not sure if I understand your use case correctly; however I recall a few years back having some success copying RADIUS accounting messages to multiple servers using the high speed logging function in irules. The basic rule is applied to a UDP virtual server which receives the message, and forwards copies of it to multiple destinations as required.
when CLIENT_ACCEPTED {
set pool_1 [HSL::open -proto UDP -pool blade_1] set pool_2 [HSL::open -proto UDP -pool blade_2] HSL::send $pool_1 [UDP::payload] HSL::send $pool_2 [UDP::payload]
}
I have a question however; it sounds like you are copying the message to all servers, when only one will end up needing to use it when the email arrives - is it worth doing something different and hashing a value which appears in both the RADIUS message, and the email, to select one server only; send the message to that server only, and then load balance the relevant email to the same server?
Or, select the pool member at random when sending the RADIUS message, write a state table entry, look it up later when the email arrives and send to the same server.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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