We have recently acquired several Ascent MAX 6000 boxes and are having a problem with a lot of duplicate RADIUS accounting packets. The problem seems to be that the MAX's are overly aggressive when sending RADIUS requests. They seem to send requests every second until the timeout seconds is reached, which seems a little extreme. When you are doing multi-hop RADIUS proxy, some accounting requests usually take a second or more.
I'm wondering if there is any way to tweak the MAX's RADIUS behavior like you can in a Cisco AS5x00 series. Normally on a Cisco you can specify the RADIUS timeout, which is the value between retry packets, the number of retries, and then the server deadtime. I really want to step the MAX's down to about 3 seconds between retries because of the hops involved. Right now we're seeing 2-3 duplicate accounting records because the MAX's are sending requests every second until the requests are ack'd. Seems overly aggressive to me. If this can be tweaked, where, and what settings should I use? Ideally I'm looking for 3 seconds between requests with 3-5 retries until it should go to the next server. Thanks in advance to anyone that can help. -- Robert Blayzor, BOFH INOC, LLC [EMAIL PROTECTED] PGP: http://www.inoc.net/~dev/ Key fingerprint = A445 7D1E 3D4F A4EF 6875 21BB 1BAA 10FE 5748 CFE9 Calm down -- it's only ones and zeroes. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.