(RADIATOR) DSL authentication queuing

[Janet N del Mundo]

Hello everyone,

Anyone out there having problems with authenticating customers AFTER a
Nortel Shasta (DSL) reboots?  

The problem that I am having is that when the Shasta reboots, DSL
customers that are trying to re-login are over populating the
authentication/accounting ports on the server.  When I do a 'netstat
-na', the ports are overwhelmed with queued processes.  Thus affecting
our regular dialup customers.  To alleviate the queued process, I
comment out the 'client clauses' that accept requests from the Shasta
for about 15-30 mins and restart radiator.   When I do this, our dialup
customers can login.  After 15-30 mins, I put back the client clauses
and restart radiator.  The queue builds up and authentication is still a
bit slow, but it's authenticating both DSL and regular dialup
customers.  Is there a better way to solve this 'congestion' with DSL
customers?

BTW, we're re-selling DSL so I don't know when the Shasta re-boots or
goes down.

I'd appreciate any comments or suggestions!
TIA,
Janet

-- 
_____________________________________________________
Janet del Mundo	
Internet Administrator, Startec Global Communications
135 Chalan Santo Papa	Agana, Guam  96910
Email: jdelmundo at corp.netpci.com
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.