Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) 6.1.7 and repeated Fatal Error 1



 Your not the only one, Look what found it's way into my network tonight:

SYSTEM IS UP:  Index: 100  Load: ftik.m40 Revision: 6.1.7e34
        Date: 09/16/1998.       Time: 04:35:47

WARNING:  Index: 140  Load: ftik.m40 Revision: 6.1.7e34
        Date: 09/18/1998.       Time: 19:50:58
        Location: b001cddc b001d094 b001d0b4 b018fc94 b01920d4 b00717a0

FATAL ERROR:  Index: 1  Load: ftik.m40 Revision: 6.1.7e34
        Date: 09/18/1998.       Time: 19:59:24
        Location: b010c374 b010d8c0 b0050214 b0050578 b018e748 b018f9c4

SYSTEM IS UP:  Index: 100  Load: ftik.m40 Revision: 6.1.7e34
        Date: 09/18/1998.       Time: 20:02:08

As I recieve more information about this I will forward it on :)

Jason Nealis
Director Internet Operations / Network Access
Erols Internet (An RCN Company)


On Fri, 18 Sep 1998, Thaddaeus Slany wrote:

> On Wed, 16 Sep 1998 20:02:09 GMT, I wrote:
> 
> >On Wed, 16 Sep 1998 00:21:05 -0400 (EDT), "Chris A. Epler" wrote:
> >
> >>On Wed, 16 Sep 1998, Thaddaeus Slany wrote:
> >>
> >>> I have never had any problems with my max 2012 running febk.m20 Rev. 6.1.7,
> >>> but today I have got two repeated fatal errors with index 1 showing exactly
> >>> same location. Before this had happened, I noticed very bad net
> >>> performance. Is there any coincidence?
> >>>
> >>> What does "Index: 1" mean?
> >                   ^^^
> >Still unanswered. Is this any sort of a memory problem? e.g memory access
> >violation? It would be nice if someone had a description of most common
> >fatal errors for MAX TAOS 6.1.x.
> >
> >>Did you 'fclear' the unit before loading 6.1.7?
> >
> >No, I updated from febk.m20 rev. 6.1.0 to febk.m20 v. 6.1.7 with one step
> >(not using a restricted load). I only did 'fsave' and 'nvramclear'
> >according to the update instructions.
> >
> >>Try tsave -am'ing your
> >>config, fclearing, trestoring the config and then restarting...this might
> >>help, I know it did on one of our boxes...
> >
> >Thank you for this tip. I hope, I will not see this fatal error 1 again.
> 
> Hi again,
> 
> too bad your tip does not work for my max. One and a half hour later I got
> same fatal error 1 again (at same location):
> 
> FATAL ERROR:  Index: 1  Load: febk.m20 Revision: 6.1.7
>         Date: 09/16/1998.       Time: 21:33:45
>         Location: b01441ec b014449c b0144cb0 b01b0f44 b01b2e20 b01b3080
>  
> SYSTEM IS UP:  Index: 100  Load: febk.m20 Revision: 6.1.7
>         Date: 09/16/1998.       Time: 21:35:23
> 
> It seems febk.m20 rev. 6.1.7 is not very stable for heavy loaded max 2012.
> 
> I will forward this to support@ascend.com as I now have a ticket number for
> this matter.
> 
> I did a clean reboot of 6.1.7 and now I will wait for the next fatal error
> 1. On weekends our traffic becomes heavier and I should better downgrade to
> more stable version. My last stable version was febk.m20 rev 6.1.0 .
> How about rev. 6.1.3 (first release with multivoice capabilities for the
> max 2000)?
> 
> Best regards
> --
> Thaddaeus Slany, Technik Buergernetzverein Guenzburg e.V.
>                  http://www.bnv-gz.baynet.de
> 
> Internet Mail: <highway@eikon.e-technik.tu-muenchen.de> or
>                <Thaddaeus.Slany@bnv-gz.baynet.de>
> 
> ++ 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>
References: