Re: (ASCEND) Pending 195 list

["Peter Rocca" <rocca@multiboard.com>]

>     >>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.

Yes, carrier was successful in both the cases (radius failure and termserv
issue), and avm showed a large number of bad calls (almost 50%) whereas our
typical rate before and after those problems is about 3% - 5% bad calls.
This is why I'm not so sure that the bad flag is only a detection of carrier
state - at least not on 7.0.4 or 7.0.26

>     >>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.

Fatal history showed:

WARNING:  Index: 195  Load: ftik.m20 Revision: 7.0.4
        Date: 05/22/2000.       Time: 18:26:29
        Location: b0099d50 b00eb21c b00ebbc4 b00ec7f4 b00ea460 b00516d8

WARNING:  Index: 196  Load: ftik.m20 Revision: 7.0.4
        Date: 05/22/2000.       Time: 18:26:29
        Location: b0099e28 b00eb21c b00ebbc4 b00ec7f4 b00ea460 b00516d8

FATAL ERROR:  Index: 1  Load: ftik.m20 Revision: 7.0.4
        Date: 05/22/2000.       Time: 18:26:43
        Location: b00982c4 b0099c9c b00eb21c b00ebbc4 b00ec7f4 b00ea460

The 195 and 196 come at the same time, and 14 seconds later an index 1 and
it rebooted.

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