Hi,
We're having a few problems with Radiator dropping radius requests from
our POP routers, and Customer routers. Around 4,000 Routers in all.
Running Radiator v2.13 on a Sun Netra T 1120 (single 300Mhz UltraSPARC-II
CPU), 128Mb RAM, Perl v5.005_02, using a Sybase SQL database on another Sun
box over 100BaseTX/FDX switched ethernet.
The database can perform upwards of 60 transactions a second
I have a plan for splitting up the load on the Radius server, as Perl is
not reliably multi-threaded, we cant use that just yet, but we can have
several instances of Radiator running.
I'm posting this out to see how viable this is, and if anyone else has a
similar setup, also as a plan if anyone else wants to increase performance
similarly.
Current config;
- Single radiator process, doing both Authentication and Accounting
Option 1;
- Set up 4 new IP Aliases on the ethernet card
- On each IP Alias, have a new Radiator process bound to it, servicing both
Authentication and Accounting
- Reconfigure all Radius clients to use a Timeout of say 2 seconds, and a
Retry of 2, and to use the new radius servers
- Let the Unix server do the processor scheduling between the Radiator
processes
Option 2;
- Same as above, but for each IP Address, launch two Radiator processes.
One for the Authentication port, and one for the Accounting port.
A few questions;
- Are there going to be any problems with having 5 or 10 simultaneous
connections to the Sybase database from the same machine?
- Is there a better way to improve performance with Radiator ?
Thanks,
Robert Moss.
Unix Systems Administrator
AAPT Limited
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
