Number of simultaneous Radius authentications per hardware platform?

  • 2
  • Question
  • Updated 4 years ago
  • Answered
As far as I know, the HiveOS Virtual Appliance supports up to 512 simultaneous Radius authentications.

Do you also have the numbers for all other platforms that can run a Radius server (AP141, AP330, ...)?

I thought this was inside the training material, but I couldn't find it... only the number for the HiveOS VA...
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes

Posted 5 years ago

  • 2
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Carsten, according to my records the number is 256 for all of the APs that can act as RADIUS servers.
Photo of Chris B

Chris B, Official Rep

  • 93 Posts
  • 10 Reply Likes
Hi Carsten

The 'tested' number is 512 across all of our products that can act as radius servers, SR2024, BR200, AP330/350, AP320/340, AP110, AP120, AP121/141& CVG.

Chris
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
In case anyone is confused by the apparent discrepancy between my and Chris' answers -- we have tested (in laboratory conditions, your mileage WILL vary) up to 256 concurrent authentication requests handled by the APs, and up to 512 authenticated users.
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Thanks guys!

Just to be sure: this is a soft limit, indicating how many are tested and verified, correct? So it might even work with more, and there is no parameter somewhere to adjust the maximum number of concurrent/authenticated users, right?
Photo of Neil Charles

Neil Charles

  • 1 Post
  • 0 Reply Likes
Can someone please explain this a little more? We have 2000 potential wireless devices across a network. Could all 2000 devices be connected to various AP's if we use a couple of 330's as the radius servers?
Photo of shoremedia

shoremedia

  • 22 Posts
  • 4 Reply Likes
I also have the a related question, with 256 concurrent authentication requests, is that in a specific timeslice, such max of 256 authentication requests can be processed if they all come in at 11:11:11am? 
Up to 512 authenticated users, does that refer to a memory table(?) limit on the AP as RADIUS to store/reference 512 users in a longer duration timeslice, such as within a 10 minute timeframe before re-authentication is required (per timeouts in policy).  Sorry for my confusion, since the AP is listed to store up to 9999 users, but are you saying that the AP as RADIUS can only support 512 of those 9999 users at one time?

I guess more info on the timeslice involved for concurrent versus authenticated users would be helpful.  Would adding more AP as RADIUS devices solve the per-AP limitation by spreading out the authentication requests as Neil Charles mentions? 
It would be easy to add a primary AP as RADIUS and a backup1 backup2, however, if the primary is limited to 256/512, then I would need to setup a completely separate primary AP as RADIUS to spread the load, which greatly complicates the matter.

Any plans for more robust RADIUS service on the AP, perhaps multiple threads to handle larger number of connections/requests if the radios are off, and AP acting as a RADIUS server only?

Reference here:
http://www.aerohive.com/330000/docs/help/english/6.1r5/hm/full/help.htm#config/auth/localUser.htm

Thanks for any feedback to clear this in my head.