[RADIATOR] EAPBALANCE and FarmSize

[Vicaretti Vincenzo (Guest)]

Hi all,

Stress-test performed has saturated the server's CPU
I have Enabling the multi-thread through the parameter FarmSize, the CPU usage goes down a lot, so we are considering the integration of support for multi-threading in our configuration.

In your documentation shows that I can use the parameter FarmSize with both AuthBy RADIUS with each its sub-balancing methods.

My back-end (Microsoft IAS) do not support the algorithm "UseContentsForDuplicateDetection." This, however, is essential to enable the FarmSize on frontend (Radiator) in combination with the EAPBALANCE balancing algorithm:

"It is essential That this parameter be defined in the Client clauses of back-end servers of an EAPBALANCE Server Farm architecture, Otherwise duplicate detection will not be performed Correctly."

I can not use the method EAPBALANCE with backend like Microsoft IAS, as I wrote in this Vatiainen Heikki mail:
http://www.open.com.au/pipermail/radiator/2013-February/018893.html

I read in your documentation:

"<AuthBy EAPBALANCE> [...] Is Intended To ensure that all EAP requests Relating to a single session always go to the same target RADIUS server"

- To balance the EAP-SIM, EAP-TLS and PEAP I am obliged to use the EAPBALANCE algorithm?

- Alternative balancing algorithms (ROUNDROBIN, VOLUMEBALANCE or LODABALANCE) maintain session persistence?

- To enable multi-threaded through the FarmSize (ServerFarm) with IAS back-end, can I use a balancing algorithm alternative? There are any contraindications?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open.com.au/pipermail/radiator/attachments/20130306/c80cd715/attachment.html