(RADIATOR) Redback is sending too many Access-Requests

[Mishari Al-Faris]

Hello All,

Our Redback is sending us Access-Requests for DSL users way too frequently,
can reach up to 1-2 requests/sec. Ofcourse the Timeout and Retry timers on
Redback are set for reasonable values like 1 retry after 30 second timeout.
All the requests coming to Radiator are being accepted, yet still sometimes
when too many users are that way our customers begin complaining about error
"718" (the computer you're dialing is not responding), in other words, the
requests are not being accepted fast enough.

We saw that after locking and unlocking the DSL port coming to Redback's ATM
interface that the user is able to login once and the requests stop.

Trying to trouble shoot this, I was wondering does Radiator have a queue for
the requests its handling? and if its possible to check its status at a
point in time? Also, when I enable Trace 4 and see an access-request appear
in the log, does that mean Radiator only received it at that exact instant?
(being reasonably close again, not talking absolute exactness) or does it
only appear in the log after it had acknowledged the request from the
Redback?

I ask this because when we get "718" errors with users and I try to login
myself, and ask a friend to have an eye on the Radiator log to see when the
request concerning me arrives.

Also, we get these in the logfile:
Tue Dec 20 08:27:36 2005: ERR: There is no value named /rb01/11/0/27/675 for
attribute Calling-Station-Id. Using 0.
Tue Dec 20 08:27:36 2005: ERR: There is no value named /rb01/11/0/27/675 for
attribute Calling-Station-Id. Using 0.

Is there a way to stop this please?

Thanks so much for you patience in reading this,
Mishary Al-Faris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20051220/6cc5e292/attachment.html>