Re: (ASCEND) Pending 195 list

[maxed_out_user@hotmail.com]

Are you sure the call has to die at the carrier detect to be considered
bad?

    >>Pretty sure.

The only two times my maxes rebooted were under situtations where the
user
wasn't authenticated, as opposed to a bad connect.

    >>Yes, but if the user failed authentication, then you must have hit
carrier state already, so "avm" wouldn't report any bad call for that
try.

The first occasion was when a new max came in and I hadn't enabled TS
logins
and one of our customers hadn't configured their machine for PAP - he
called
about 50 times in a row and unfortunately all of those calls terminated
on
one max box. The box reset and while it was down our calls routed to a
second box that had TS enabled so he got connected.

    >>I think if terminal server is disabled, a modem user should still
reach carrier detect state before it figures out no terminal server is
available.  When this user failed 50 times in a row, did "avm" show any
suspect modems or excessive "bad calls"?  Otherwise, I think that was a
different cause of your reboot.

The second occasion was when our radius server failed, all new calls
coming
in were dropped and the box rebooted a couple minutes later. Once I
reset
the radius server everything was normal again.

    >>If the RADIUS server fails, users will still be able to get
connected successfully modemwise, but then authentication will fail.
Again, if you're Max rebooted here, it's a different case than what I
was talking about.

I'd agree it would make a lot more sense for the 'bad' flag to only be
assigned on data link level failures, but from my experience I'm no so
sure
that is the way it is...

    >>I think you're historical reboots were for some other reason.  I
was talking about reboots occuring due to the Warning 195s so they fixed
it by putting in the "Pending 195" counter.

> When a modem on a slot card gets up to 8 consecutive bad calls (a bad
> call would be classified as a call which never made it to carrier
detect
> state), the Max will place this modem in a suspect list.  Suspect
> doesn't mean the modem is disabled, but rather it's in a last priority

> to be used list.  So if all the other modems are in use, then it will
> try and route analog calls to any modems on the suspect list.  If the
> modem in the suspect list happens to answer a call successfully, then
it
> will be taken out of suspect status and into the regular pool of free
> modems; otherwise, it remains in the suspect list and just racks up
> another bad call.
> What you need to do is investigate why the modems get on the suspect
> list in the first place.  If you consistently get a lot of bad calls,
> you should check your T1 lines and see if you have a line problem.  If

> they look like they're running clean, then constantly issue the "avm"
> command now and then and see if the same modem on a particular slot
card
> is going on the suspect list (or getting a lot of bad calls).  If it's

> the same modem all the time, then I would think you have a bad modem
and
> need to RMA the card.  If it's always a different modem, then I think
it
> might just be a line problem.

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>