> * Has anyone run across this, we had approximately 30 radius accounting > records come from one Max 6000 (ebaxk.m60 Revision: 7.0.3) with gigs of session > time. This hiccup seems to have happened over a 30-minute time frame. > > Any suggestions are appreciated. This sure put a fly in the ointment of the > tracking of user session time. We had to pull out these 30 or so records > Acct-Session-Time and rerun reports. Do you by any chance run NTP? We had this happen, when we had NTP turned on on our Maxen. Here's the scenario: - Max boots up, thinking it is some time in 1970 (I believe, don't remember correctly if it was 1970 or some other year). - Users start comming in and login successfully. - While the first couple of users are logged in, Max uses NTP to sync time, so the time jumps forward by a couple of decades. - Max thinks user is logged on for a couple of decades and when the user logs off, this is recorded in the radius logs. Lucent is aware of this problem, but to my knowledge has not done anything yet to fix it (I reported it a couple of months ago, with an exact description of the circumstances and a Lucent engineer confirmed that my conclusions were correct). My fix was to turn off NTP. We are running 7.2.3 on our Maxen. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz at amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>