Hello Julio -
On Friday 02 February 2001 19:05, [EMAIL PROTECTED] wrote:
> In our scenario:
>
> 3x Radiator servers (u5, u60, PII)
> 1x Arrowpoint LB (CSS11000)
> 1x Mysql (U250)
> 1x LDAP (U250)
> 3x Clients with radpwtst (U220R, Alpha)
>
> Clients send 1000 requests with radpwtst with -nostop. The clients are
> always at 100% CPU.
> They finish the requests in 150 seg, and we obtain a lot of "No reply"'s.
>
> The RADPOOL only updates 600 registers, and accounting insert 800 users (a
> lot of them with blank framedipaddress).
>
> These blank framedipaddres we think that they are due to radpwtst which
> sends always auth and acct packets. If an auth is not answered, radpwtst
> sends the acct and of course, RADONLINE is updated with an user with blank
> ip address because of auth was not resolved.
>
> Another thing is that with Radiator 2.16.3, we update 1000 of 1000 requests
> in RADONLINE (with duplicate ip's) RADPOOL has 600 registers updated and we
> haven't "No reply" messages in radpwtst client application.
>
> We upgrade Radiator to 2.17.1 to resolve the problem of "ip racing" in
> RADPOOL and, yes, we have not duplicates in RADONLINE but otherwise we
> obtain "No reply"'s, only 800 user registered in RADONLINE and, 'blank'
> framedipaddress in RADONLINE.
>
> We read some Radiator documentation that says '160 requests per second'. So
> certainly we are doing something wrong.
>
> All your experience will be appreciated, and help is needed urgently.
>
I have copied this to Mike so he can add his comments also.
Could you please explain what you are trying to simulate with your testing?
And could you also please send us copies of your configuaration file(s) (no
secrets), copies of your startup scripts, copies of your radpwtst scripts and
any relevant trace 4 debug output?
If you are only trying to test maximum authentication rates, you should be
using "radpwtst -noacct .....". You should also set up a base-line scenario
with just an AuthBy TEST, or a simple AuthBy FILE to see how fast Radiator
runs with no outside influences, then you can add components to your testing
progressively and you will be able to see what components are taking the most
time.
Note that Mike has done some work over the last couple of weeks on the
AddressAllocatorSQL code to improve its performance significantly.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.
