There is a three second timeout on the Radius server as far as the
PM is concerned. So if the PM sends the accounting, the server is
really busy and doesn't get back until say five seconds, the PM will
send it again, and again, until it gets a response back within three
seconds. Accounting packates are queued in the PM until a ACK comes
back from the Radius server.
You can see if this is hapenning by looking at the Acct-Delay field
for each packet. Generally it will increase for each packet received
by the Radius server, where the below four fields are the same.
> On a related question, is there any possiblity that two PortMasters
> would produce the same session ID in the period of a month. Is there
> something about the way the ID's are created that prevents this?
Each Accounting Record is unique via these four keys:
NAS-Identifier
NAS-Port
Acct-Session-ID
Acct-Status-Type
We store out accounting into a database and put a unique key contraint
on those, and it prevents the problem you are talking about. There is NO
guranteed uniqeness less than thos four keys. Acct-Session-ID by itself
is not unique.
-- Dale E. Reed Jr. (daler@iea.com) _____________________________________________________________________ Internet Engineering Associates | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea.com/~daler