Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Radius accounting
Michael,
You are pretty closed. What I am after is the stop record
before the MAX re-start or crash...
From: "Michael Curran" <mcurran@csu.edu.au>
Organization: Charles Sturt University
To: ascend-users@max.bungi.com
Date sent: Fri, 10 Jul 1998 16:58:44 +1000
Subject: Re: (ASCEND) Radius accounting
Send reply to: mcurran@csu.edu.au
Copies to: vninfo@ca.com.au
Priority: normal
> > Date: Fri, 10 Jul 1998 12:19:11 +0800
> > From: "Vinh NGO" <vninfo@ca.com.au>
> > To: ascend-users@max.bungi.com
> > Subject: (ASCEND) Radius accounting
>
> > I have ISDN users connected to our MAX4000.
> >
> > I have radius to disconnect users after 1 week connection to
> > collect stat for accounting.
> >
> > My question is if the MAX reset before I disconnect users and
> > collect stat, then my 1 week long stat lost. I don't want to
> > discconect user every day either.
> >
> > Any one have a work around this? I am thinking of a polling
> > daemon to collect stat using SNMP and manually collect stat
> > if the MAX reset.
> >
> >
> if I understand you correctly, you want to process your accounting
> file from week to week and you're concerned about what happens if
> RADIUS stops or the MAX falls over in that period.
>
> I have a Perl script that stops RADIUS, renames the 'detail' files
> and then re-starts RADIUS (within a couple of seconds) so I have
> distinct weekly accounting files for processing. That way I have
> a record of activity for each MAX for each week and can process
> them without affecting the current accounting records. Its' pretty
> easy... and I'm happy to share the script with you if you want.
>
> As far as RADIUS falling over .. well, when you re-start it, the
> accounting information continues to be written to the same 'detail'
> file as it always was... so you lose whatever transacted between the
> failure and the re-start. UNLESS you have a secondary (backup) RADIUS
> server.
>
> If you are keen on monitoring calls using SNMP, I recently wrote a
> script in Perl that monitors MAX usage and kills users who have been
> on the longest (according to some rules). I'm happy to share it with
> you if you would like a copy.
>
> Hope this helps you.
>
> Regards,
>
>
>
>
> Michael
>
> -------------------------------------------------------------------
> - Michael Curran mcurran@csu.edu.au -
> - http://athene.mit.csu.edu.au/~mcurran -
> -------------------------------------------------------------------
> - Information Technology Officer Charles Sturt University -
> - Online Support & Systems Programming -
> -------------------------------------------------------------------
> - "Confidence, like art, never comes from having all the answers; -
> - it comes from being open to all the questions" -
> - Earl Gary Stevens -
> -------------------------------------------------------------------
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: