Check the Acct-Delay-Time. If they the same Acct-Status and Acct-Session-Id
but different Acct-Delay-Time, it means the PortMaster didn't get the
accounting-response packet from the RADIUS server and sent the
accounting-request again when the backoff timer expired. Its harmless.
> 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?
Its certainly possible for two PortMasters to produce the same session ID!
Session ID is only unique to a given NAS; if you want something unique
across NASes you should append the Client-Id.
Note that if you reflash a PortMaster's NVRAM to factory spec that it'll
start over on its Acct-Session-Ids after the next reboot, but that shouldn't
surprise anyone.
For PortMasters, the Acct-Session-Id is 8 hexadecimal digits; the top 2
are the number of times its rebooted with accounting turned on, the
next 6 are the number of logins since the last reboot. If you have
more than 16 million logins between reboots, 1) the lower part of the
Acct-Session-Id will probably wrap around, 2) please contact our
Marketing department because they'd probably like to get a testimonial
out of you. :-)
16 million users on a PM-2E-30 is a user logging in and back out every
minute on every port for a solid year, with no reboot or upgrade for the
entire year.
-- Carl