Real Time Ascend Maling List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: (ASCEND) AAC RADIUS NT Crashing!
Just as a warning to everybody: Call-logging should NOT be used as a
substitute for Radius.
Call-logging was designed for use ONLY with Lucent's NavisAccess management
product. However, it was in some instances documented as being a substitute
for Radius. This was a mistake. Furthermore, with the 7.2 release of TAOS,
call-logging begins a significant divergence from Radius, and it WILL cause
problems with Radius servers.
Going forward, please do NOT use call-logging as a Radius substitute,
because it will not work. Again, call-logging is designed specifically to
provide data to NavisAccess, and it does NOT attempt to adhere to any Radius
standards.
Peter Eicher
NavisAccess Marketing Manager
> -----Original Message-----
> From: owner-ascend-users@max.bungi.com
> [mailto:owner-ascend-users@max.bungi.com]On Behalf Of Rogers, Kirk
> Sent: Sunday, October 18, 1998 5:51 PM
> To: 'Tom Wagoner'; ascend-users@bungi.com; support@ascend.com
> Cc: 'Robert Rozsa'
> Subject: RE: (ASCEND) AAC RADIUS NT Crashing!
>
>
> This is starting to make sense...thanks Tom for the addition
> clues. I have
> been seeing the same strange characters, but didn't think it was related.
> I think I've isolated it to a specific NAS server from another division
> within my company, who we've been monitoring and managing their accounting
> data from the 'Call Logging' output. The 'Call Logging' output from their
> particular NAS server was pointing to my primary RADIUS server with no
> secondary or third server. My secondary RADIUS server was never crashing!
> During all my testing (for about 7 weeks now) I've been shutting down
> services on by one, in an effort to isolate the problem. All the
> while the
> 'Call Logging' from this other division was never changed. So I
> decided to
> do an extensive memory test on the primary RADIUS server and the
> only thing
> I changed on the NAS severs was the other divisions 'Call Logging' IP
> address to point to my secondary RADIUS server. For the first time ever,
> RADIUS crashed about two hours latter!!!!!
> So, I turned off the 'Call Logging' from that particular server and so far
> so good...no RADIUS crashes. I need to let this configuration
> run for a few
> more days to eliminate the possibility of coincidence, but the
> RADIUS server
> in question was crashing at a daily rate. Its been good now since Friday
> afternoon...getting close to the longest time up since the
> problem started.
> Once I confirm this suspicion, I will go back to see who was logging in at
> the time of the crashes from the accounting records of the other division
> and isolate the potential user/accounting/call logging records???
> Not sure
> of what I'll find...
>
> Kirk
>
>
>
> -----Original Message-----
> From: Tom Wagoner [mailto:pcmentor@waveone.net]
> Sent: Friday, October 16, 1998 11:36 AM
> To: Rogers, Kirk; ascend-users@bungi.com;
> support@ascend.com
> Cc: 'Robert Rozsa'
> Subject: RE: (ASCEND) AAC RADIUS NT Crashing!
>
> I am having this same problem but it started on October 1st.
> Ran fine for
> months before.
>
> The line right before the exception line show a user id of
> garbage
> information tring to be authenticated. It either is random
> characters or
> blank space before and after the valid user id.
>
> Anyone else seeing this.
>
> Please help.
>
> Tom Wagoner
> System Administrator
> WaveOne Communications, LLC
> Ph: 219.267.5370
> Fax: 219.267.1565
> E-mail: pcmentor@waveone.net
>
>
> > -----Original Message-----
> > From: owner-ascend-users@max.bungi.com
> > [mailto:owner-ascend-users@max.bungi.com]On Behalf Of
> Rogers, Kirk
> > Sent: Thursday, October 15, 1998 6:05 AM
> > To: 'ascend-users@bungi.com'; 'support@ascend.com'
> > Cc: 'Robert Rozsa'
> > Subject: (ASCEND) AAC RADIUS NT Crashing!
> >
> >
> > Like the subject says,
> > AAC RADIUS is now crashing almost at a daily rate. The
> biggest
> > problem here
> > is that there are no indications anywhere, other than the
> logfile which
> > simply states:
> >
> > Wed Oct 14 16:19:27 1998: RadiusSrvMain: structured
> exception handler
> > entered
> >
> > This has been going on for some time now, and it's killing
> me. Our
> > configuration is the same on two different servers yet
> only one
> > is crashing:
> > NT4.0 sp3
> > AAC Ai11
> > MSSQL
> >
> > If anyone has seen something similar, please let me know
> where to look for
> > resolution.
> >
> >
> > ++ Ascend Users Mailing List ++
> > To unsubscribe: send unsubscribe to
> ascend-users-request@bungi.com
> > To get FAQ'd: <http://www.nealis.net/ascend/faq>
> >
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to
> ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>