Re: [RADIATOR] Use FarmSize parameter

[Alan Buxey]

Like the farmsize.cfg file in the goodies directory?

alan___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[A . L . M . Buxey]

Hi,

>So what happens to the EAP/PEAP requests if one enables FarmSize?  Do they
>simply get processed by the parent, or do they break completely?

the issue is to ensure that the same child deals with them.
if you are running 4.15 + patches then there is a whoie nice new Gossip
framework which is very easy to get up and running to share the 
state between all children and ensure the request gets dealt with correctly.

try it (in test/lab/bench environment)thats really the best way.


alan
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[Barry Ard]

The key is to use the eapbalance handler with farmsize and then proxy to
individual "backend" processes that handle the eap details / authentication.

This is outlined in goodies/eapbalance.cfg.

Barry

On Fri, Sep 25, 2015 at 8:22 AM, Garry Shtern <garry.sht...@twosigma.com>
wrote:

> So what happens to the EAP/PEAP requests if one enables FarmSize?  Do they
> simply get processed by the parent, or do they break completely?
>
>
>
> *From:* radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au]
> *On Behalf Of *Amândio Antunes Gomes Silva
> *Sent:* Thursday, September 24, 2015 4:43 AM
> *To:* António Mendes <antonio.men...@wit-software.com>;
> radiator@open.com.au
> *Subject:* Re: [RADIATOR] Use FarmSize parameter
>
>
>
> Hi António (and the rest)!
>
>
>
> From the Radiator 4.15 Reference Manual (Section 5)
>
> 5.7.43FarmSize
>
> This optional parameter allows you to specify how many server instances to
> create in a server farm. A server farm is a set of identical Radiator
> servers, all monitoring the same RADIUS sockets. Incoming RADIUS requests
> are distributed among the child servers in the server farm. The main server
> acts as a supervisor, and restarts children that die or are terminated.
> Unix only. Defaults to 0, which means no server farm, and only a single
> instance of Radiator is run.
>
> Hint: this parameter can be used to improve performance in some cases on
> platforms that support multiple cores and fork().
>
> Caution: This parameter, and the use of server farms is not compatible
> with many EAP protocols, such as TLS, TTLS, PEAP etc. This is because such
> protocols rely in authentication state being held within each server
> process, and it is necessary for all the requests for such protocols to go
> to the same Radiator instance.
>
>
>
> So you have to make sure that the platform where you have Radiator running
> on supports what’s mentioned in *Hint*.
>
>
>
> Regards,
>
>
>
> Cumprimentos,
>
> *Amândio Antunes Gomes da Silva*
>
>
> ---
>
> Serviços de Comunicações da Universidade do Minho
>
> Campus de Gualtar, 4710-057 Braga - Portugal
>
> Tel.: + 351 253 60 40 20, Fax: +351 253 60 40 21
>
> email: aman...@scom.uminho.pt | http://www.scom.uminho.pt
>
>
> ---
>
> This email is confidential. If you are not the intended recipient,
>
> you must not disclose or use the information contained in it.
>
> If you have received this mail in error, please tell us immediately
>
> by return email and delete the document.
>
> --
>
> Este email é confidêncial. Se não é o destinatário do mesmo,
>
> não deve nem revelar, nem usar o seu conteúdo.
>
> Se recebeu esta mensagem por engano, por favor informe-nos
>
> Imediatamente, devolvendo e apagando este email.
>
>
>
>
>
>
>
>
>
>
>
> *De:* António Mendes [mailto:antonio.men...@wit-software.com
> <antonio.men...@wit-software.com>]
> *Enviada:* quarta-feira, 23 de setembro de 2015 15:40
> *Para:* radiator@open.com.au
> *Assunto:* [RADIATOR] Use FarmSize parameter
>
>
>
> Hello all,
>
> We are running a scenario with an instance acting as a father and
> forwarding the traffic for children processes according to some parameters
> in request. We done that changing the init script and starting several
> instances of radiator(each one in a different port).
>
> We are noticing that the father process are consuming too much processing
> resources and is only using one core, we would like to change this
> configuration to allow the distribution of load for all CPU cores available
> in the server and to do that we are thinking to use "FarmSize" and create
> several instances of father process.
>
> Do you see any problem with this new approach(I'm a little bit worried
> about the write concurrency of log files)? Do you have any concern or
> recommendations?
>
>
> Thanks
>
> --
>
> António Mendes
>
> WIT Software | Software Engineer
>
> This email was sent under WIT Software's Confidentiality Policy
> <https://www.wit-software.com/confidentiality-policy/>
>
> ___
> radiator mailing list
> radiator@open.com.au
> http://www.open.com.au/mailman/listinfo/radiator
>



-- 

Barry Ard   barry@ualberta.ca
IST
University of Alberta
Edmonton, Alberta   Canada
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[Garry Shtern]

It would be helpful to have a sample configuration that includes all of this...

-Original Message-
From: a.l.m.bu...@lboro.ac.uk [mailto:a.l.m.bu...@lboro.ac.uk] 
Sent: Friday, September 25, 2015 11:44 AM
To: Garry Shtern <garry.sht...@twosigma.com>
Cc: 'Amândio Antunes Gomes Silva' <aman...@scom.uminho.pt>; António Mendes 
<antonio.men...@wit-software.com>; radiator@open.com.au
Subject: Re: [RADIATOR] Use FarmSize parameter

Hi,

>So what happens to the EAP/PEAP requests if one enables FarmSize?  Do they
>simply get processed by the parent, or do they break completely?

the issue is to ensure that the same child deals with them.
if you are running 4.15 + patches then there is a whoie nice new Gossip 
framework which is very easy to get up and running to share the state between 
all children and ensure the request gets dealt with correctly.

try it (in test/lab/bench environment)thats really the best way.


alan
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[Garry Shtern]

So what happens to the EAP/PEAP requests if one enables FarmSize?  Do they 
simply get processed by the parent, or do they break completely?

From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On 
Behalf Of Amândio Antunes Gomes Silva
Sent: Thursday, September 24, 2015 4:43 AM
To: António Mendes <antonio.men...@wit-software.com>; radiator@open.com.au
Subject: Re: [RADIATOR] Use FarmSize parameter

Hi António (and the rest)!

From the Radiator 4.15 Reference Manual (Section 5)

5.7.43FarmSize

This optional parameter allows you to specify how many server instances to 
create in a server farm. A server farm is a set of identical Radiator servers, 
all monitoring the same RADIUS sockets. Incoming RADIUS requests are 
distributed among the child servers in the server farm. The main server acts as 
a supervisor, and restarts children that die or are terminated. Unix only. 
Defaults to 0, which means no server farm, and only a single instance of 
Radiator is run.

Hint: this parameter can be used to improve performance in some cases on 
platforms that support multiple cores and fork().

Caution: This parameter, and the use of server farms is not compatible with 
many EAP protocols, such as TLS, TTLS, PEAP etc. This is because such protocols 
rely in authentication state being held within each server process, and it is 
necessary for all the requests for such protocols to go to the same Radiator 
instance.

So you have to make sure that the platform where you have Radiator running on 
supports what’s mentioned in Hint.

Regards,

Cumprimentos,
Amândio Antunes Gomes da Silva
---
Serviços de Comunicações da Universidade do Minho
Campus de Gualtar, 4710-057 Braga - Portugal
Tel.: + 351 253 60 40 20, Fax: +351 253 60 40 21
email: aman...@scom.uminho.pt<mailto:aman...@scom.uminho.pt> | 
http://www.scom.uminho.pt<http://www.scom.uminho.pt/>
---
This email is confidential. If you are not the intended recipient,
you must not disclose or use the information contained in it.
If you have received this mail in error, please tell us immediately
by return email and delete the document.
--
Este email é confidêncial. Se não é o destinatário do mesmo,
não deve nem revelar, nem usar o seu conteúdo.
Se recebeu esta mensagem por engano, por favor informe-nos
Imediatamente, devolvendo e apagando este email.





De: António Mendes [mailto:antonio.men...@wit-software.com]
Enviada: quarta-feira, 23 de setembro de 2015 15:40
Para: radiator@open.com.au<mailto:radiator@open.com.au>
Assunto: [RADIATOR] Use FarmSize parameter

Hello all,

We are running a scenario with an instance acting as a father and forwarding 
the traffic for children processes according to some parameters in request. We 
done that changing the init script and starting several instances of 
radiator(each one in a different port).

We are noticing that the father process are consuming too much processing 
resources and is only using one core, we would like to change this 
configuration to allow the distribution of load for all CPU cores available in 
the server and to do that we are thinking to use "FarmSize" and create several 
instances of father process.

Do you see any problem with this new approach(I'm a little bit worried about 
the write concurrency of log files)? Do you have any concern or recommendations?


Thanks
--

António Mendes

WIT Software | Software Engineer

This email was sent under WIT Software's Confidentiality 
Policy<https://www.wit-software.com/confidentiality-policy/>
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[António Mendes]

Hi Hugh, thanks for your answer.

The "father" process is consuming too much CPU due to the amount of 
requests, it's perfectly normal because we have a huge amount of 
clients. The Radiator's performance it's not a problem.
We need to move forward because we see that the hardware it's 
underused(one CPU core reaches several time 100% of use but the others 
are unused).  To avoid this problem and make use of all cores available 
we take a look of "Farmsize" feature, but like I said we are a bit 
worried about problems that could arise, like concurrency problems. So 
my question is if there are known problems in use the Farmsize, or do 
you advise to upgrade the configuration in another way.


Please note that we are thinking to use the Farmsize in accounting 
process, so the known authentication problems will not be a problem for us.


Best regards,

António Mendes

WIT Software | Software Engineer

This email was sent under WIT Software's Confidentiality Policy 



Às 07:38 de 24-09-2015, Hugh Irvine escreveu:

Hello Antonio -

I am curious to know why your “father” process is taking so much time?

Have you checked a trace 4 debug with LogMicroseconds enabled to see what 
exactly is taking the time?

If you send me a copy of your configuration file(s) directly, I will take a 
look and try to make some suggestions.

FarmSize can be used in some situations, but it can cause problems in other 
situations.

regards

Hugh



On 24 Sep 2015, at 00:40, António Mendes  
wrote:

Hello all,

We are running a scenario with an instance acting as a father and forwarding 
the traffic for children processes according to some parameters in request. We 
done that changing the init script and starting several instances of 
radiator(each one in a different port).

We are noticing that the father process are consuming too much processing resources and 
is only using one core, we would like to change this configuration to allow the 
distribution of load for all CPU cores available in the server and to do that we are 
thinking to use "FarmSize" and create several instances of father process.

Do you see any problem with this new approach(I'm a little bit worried about 
the write concurrency of log files)? Do you have any concern or recommendations?


Thanks
--
António Mendes

WIT Software | Software Engineer

This email was sent under WIT Software's Confidentiality Policy

___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator


--

Hugh Irvine
h...@open.com.au

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc.
Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc.



___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[Hugh Irvine]

Hello Antonio -

I am curious to know why your “father” process is taking so much time?

Have you checked a trace 4 debug with LogMicroseconds enabled to see what 
exactly is taking the time?

If you send me a copy of your configuration file(s) directly, I will take a 
look and try to make some suggestions.

FarmSize can be used in some situations, but it can cause problems in other 
situations.

regards

Hugh


> On 24 Sep 2015, at 00:40, António Mendes  
> wrote:
> 
> Hello all,
> 
> We are running a scenario with an instance acting as a father and forwarding 
> the traffic for children processes according to some parameters in request. 
> We done that changing the init script and starting several instances of 
> radiator(each one in a different port).
> 
> We are noticing that the father process are consuming too much processing 
> resources and is only using one core, we would like to change this 
> configuration to allow the distribution of load for all CPU cores available 
> in the server and to do that we are thinking to use "FarmSize" and create 
> several instances of father process.
> 
> Do you see any problem with this new approach(I'm a little bit worried about 
> the write concurrency of log files)? Do you have any concern or 
> recommendations?
> 
> 
> Thanks
> -- 
> António Mendes
> 
> WIT Software | Software Engineer
> 
> This email was sent under WIT Software's Confidentiality Policy
> 
> ___
> radiator mailing list
> radiator@open.com.au
> http://www.open.com.au/mailman/listinfo/radiator


--

Hugh Irvine
h...@open.com.au

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc. 
Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc.

___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[Amândio Antunes Gomes Silva]

Hi António (and the rest)!

From the Radiator 4.15 Reference Manual (Section 5)

5.7.43FarmSize

This optional parameter allows you to specify how many server instances to 
create in a server farm. A server farm is a set of identical Radiator servers, 
all monitoring the same RADIUS sockets. Incoming RADIUS requests are 
distributed among the child servers in the server farm. The main server acts as 
a supervisor, and restarts children that die or are terminated. Unix only. 
Defaults to 0, which means no server farm, and only a single instance of 
Radiator is run.

Hint: this parameter can be used to improve performance in some cases on 
platforms that support multiple cores and fork().

Caution: This parameter, and the use of server farms is not compatible with 
many EAP protocols, such as TLS, TTLS, PEAP etc. This is because such protocols 
rely in authentication state being held within each server process, and it is 
necessary for all the requests for such protocols to go to the same Radiator 
instance.

So you have to make sure that the platform where you have Radiator running on 
supports what’s mentioned in Hint.

Regards,

Cumprimentos,
Amândio Antunes Gomes da Silva
---
Serviços de Comunicações da Universidade do Minho
Campus de Gualtar, 4710-057 Braga - Portugal
Tel.: + 351 253 60 40 20, Fax: +351 253 60 40 21
email: aman...@scom.uminho.pt<mailto:aman...@scom.uminho.pt> | 
http://www.scom.uminho.pt<http://www.scom.uminho.pt/>
---
This email is confidential. If you are not the intended recipient,
you must not disclose or use the information contained in it.
If you have received this mail in error, please tell us immediately
by return email and delete the document.
--
Este email é confidêncial. Se não é o destinatário do mesmo,
não deve nem revelar, nem usar o seu conteúdo.
Se recebeu esta mensagem por engano, por favor informe-nos
Imediatamente, devolvendo e apagando este email.





De: António Mendes [mailto:antonio.men...@wit-software.com]
Enviada: quarta-feira, 23 de setembro de 2015 15:40
Para: radiator@open.com.au
Assunto: [RADIATOR] Use FarmSize parameter

Hello all,

We are running a scenario with an instance acting as a father and forwarding 
the traffic for children processes according to some parameters in request. We 
done that changing the init script and starting several instances of 
radiator(each one in a different port).

We are noticing that the father process are consuming too much processing 
resources and is only using one core, we would like to change this 
configuration to allow the distribution of load for all CPU cores available in 
the server and to do that we are thinking to use "FarmSize" and create several 
instances of father process.

Do you see any problem with this new approach(I'm a little bit worried about 
the write concurrency of log files)? Do you have any concern or recommendations?


Thanks
--

António Mendes

WIT Software | Software Engineer

This email was sent under WIT Software's Confidentiality 
Policy<https://www.wit-software.com/confidentiality-policy/>
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Use FarmSize parameter

[Hugh Irvine]

Hi Antonio -

I would need to see your configuration file(s) before making suggestions.

If you send copies to me directly I will take a look.

regards

Hugh


> On 24 Sep 2015, at 18:10, António Mendes  
> wrote:
> 
> Hi Hugh, thanks for your answer.
> 
> The "father" process is consuming too much CPU due to the amount of requests, 
> it's perfectly normal because we have a huge amount of clients. The 
> Radiator's performance it's not a problem.
> We need to move forward because we see that the hardware it's underused(one 
> CPU core reaches several time 100% of use but the others are unused).  To 
> avoid this problem and make use of all cores available we take a look of 
> "Farmsize" feature, but like I said we are a bit worried about problems that 
> could arise, like concurrency problems. So my question is if there are known 
> problems in use the  Farmsize, or do you advise to upgrade the configuration 
> in another way.
> 
> Please note that we are thinking to use the Farmsize in accounting process, 
> so the known authentication problems will not be a problem for us.
> 
> Best regards,
> António Mendes
> 
> WIT Software | Software Engineer
> 
> This email was sent under WIT Software's Confidentiality Policy
> 
> Às 07:38 de 24-09-2015, Hugh Irvine escreveu:
>> Hello Antonio -
>> 
>> I am curious to know why your “father” process is taking so much time?
>> 
>> Have you checked a trace 4 debug with LogMicroseconds enabled to see what 
>> exactly is taking the time?
>> 
>> If you send me a copy of your configuration file(s) directly, I will take a 
>> look and try to make some suggestions.
>> 
>> FarmSize can be used in some situations, but it can cause problems in other 
>> situations.
>> 
>> regards
>> 
>> Hugh
>> 
>> 
>> 
>>> On 24 Sep 2015, at 00:40, António Mendes 
>>>  wrote:
>>> 
>>> Hello all,
>>> 
>>> We are running a scenario with an instance acting as a father and 
>>> forwarding the traffic for children processes according to some parameters 
>>> in request. We done that changing the init script and starting several 
>>> instances of radiator(each one in a different port).
>>> 
>>> We are noticing that the father process are consuming too much processing 
>>> resources and is only using one core, we would like to change this 
>>> configuration to allow the distribution of load for all CPU cores available 
>>> in the server and to do that we are thinking to use "FarmSize" and create 
>>> several instances of father process.
>>> 
>>> Do you see any problem with this new approach(I'm a little bit worried 
>>> about the write concurrency of log files)? Do you have any concern or 
>>> recommendations?
>>> 
>>> 
>>> Thanks
>>> -- 
>>> António Mendes
>>> 
>>> WIT Software | Software Engineer
>>> 
>>> This email was sent under WIT Software's Confidentiality Policy
>>> 
>>> ___
>>> radiator mailing list
>>> 
>>> radiator@open.com.au
>>> http://www.open.com.au/mailman/listinfo/radiator
>> 
>> --
>> 
>> Hugh Irvine
>> 
>> h...@open.com.au
>> 
>> 
>> Radiator: the most portable, flexible and configurable RADIUS server 
>> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
>> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
>> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
>> DIAMETER, SIM, etc. 
>> Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc.
>> 
>> 
> 


--

Hugh Irvine
h...@open.com.au

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc. 
Full source on Unix, Linux, Windows, MacOSX, Solaris, VMS, NetWare etc.

___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

[RADIATOR] Use FarmSize parameter

[António Mendes]

Hello all,

We are running a scenario with an instance acting as a father and 
forwarding the traffic for children processes according to some 
parameters in request. We done that changing the init script and 
starting several instances of radiator(each one in a different port).


We are noticing that the father process are consuming too much 
processing resources and is only using one core, we would like to change 
this configuration to allow the distribution of load for all CPU cores 
available in the server and to do that we are thinking to use "FarmSize" 
and create several instances of father process.


Do you see any problem with this new approach(I'm a little bit worried 
about the write concurrency of log files)? Do you have any concern or 
recommendations?



Thanks
--

António Mendes

WIT Software | Software Engineer

This email was sent under WIT Software's Confidentiality Policy 



___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator