I'm curious, Did you open a TR ticket with Ascend on it, I got the "We have never seen that problem before " quote when I reported it. I have a hard time believing it was just me. Jason Nealis On Fri, 7 Nov 1997, Andre Beck wrote: > Hi, > > On Wed, Nov 05, 1997 at 03:04:57AM -0500, Jason Nealis wrote: > > > > I'm curious if any of you have seen the following , On my 1800's > > I upgraded to AP33, I've had a number of failures, The boxes go into > > a reboot cycle and never come out of it, Have you seen this? > > > > FATAL ERROR: Index: 19 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 20:01:16 > > Location: b012678c b01270d4 b0127d48 b01c26b0 b01c2814 b0089878 > > > > WARNING: Index: 106 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 20:01:16 > > Location: b017c924 b01a23a8 b01a45e8 b008b180 b008b0a8 b012678c > > > > FATAL ERROR: Index: 19 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 20:02:18 > > Location: b012678c b01270d4 b0127d48 b01c26b0 b01c2814 b0089878 > > > > > fat > > FATAL ERROR: Index: 19 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 20:01:16 > > Location: b012678c b01270d4 b0127d48 b01c26b0 b01c2814 b0089878 > > > > WARNING: Index: 106 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 20:01:16 > > Location: b017c924 b01a23a8 b01a45e8 b008b180 b008b0a8 b012678c > > > > FATAL ERROR: Index: 19 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 20:02:18 > > Location: b012678c b01270d4 b0127d48 b01c26b0 b01c2814 b0089878 > > *BINGO* > > We should call this the Max1800 instobooting problem. We have seen this > with several Max1800 units during the last months, first (and most in- > tensely when upgrading to p13). These units, working perfectly up to the > day the p13 was installed, crashed right during boot and got into a reboot > loop (this is the death of unattended remote upgrades). We had units where > a powerdown of some minutes caused the 1800 to come back alive and further > cleansweeping of the config (fclear,trestore,fsave,nvram) seemed to cure > it somewhat. We had a unit where only removal of the NVRAM backup battery > got the unit back alive, but the unit crashed again after installing the > previous config onto it (RMA'ed this one). When we had a chance to look on > these faulty units we saw Net/BRI as "Not avail" - may be an indication > of failing POST as seen with modem slots. > > This problem seemed to went away with anything after p13, but this may also > have been a strange coincidence. May also be that it happens only now and > then, and only to some range of S/Ns. Bad enough, it happened as well with > p33 on one of our remote 1800s giving us a bad time (it's good to have > relatives in towns where you install remote Ascends...). > > > Also another issue with AP33 is I'm getting Fatal Error #2's, > > Have you seen these? > > > > Date: 11/04/1997. Time: 21:12:30 > > NVRAM was rebuilt > > > > SYSTEM IS UP: Index: 100 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 21:12:53 > > > > FATAL ERROR: Index: 2 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 22:17:14 > > Location: b017ca7c b0089438 b0089e34 b00a803c b00a80a0 b0088848 > > > > SYSTEM IS UP: Index: 100 Load: bi.m18 Revision: 5.0Ap33 > > Date: 11/04/1997. Time: 22:18:21 > > Haven't seen this yet, but your base is mucho greater than mine - for > you the "law of the big number" holds better ;) > > *Sigh* > > Andre. > -- > > Kanther-Line: PGP SSH IDEA MD5 GOST RIPE-MD160 3DES RSA FEAL32 RC4 > > +-o-+--------------------------------------------------------+-o-+ > | o | \\\- Brain Inside -/// | o | > | o | ^^^^^^^^^^^^^^ | o | > | o | Andre' Beck (ABPSoft) beck@ibh-dd.de XLink PoP Dresden | o | > +-o-+--------------------------------------------------------+-o-+ > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to ascend-users-request@bungi.com > To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <STRONG>Follow-Ups</STRONG>: <UL> <LI><STRONG><A HREF="msg10533.html">Re: (ASCEND) Firmware for MAX 1800</A></STRONG></LI> <UL> <LI><EM>From</EM>: Andre Beck <beck@ibh-dd.de></LI> </UL> </UL> <!--X-Follow-Ups-End--> <!--X-References--> <STRONG>References</STRONG>: <UL> <LI><STRONG><A HREF="msg10519.html">Re: (ASCEND) Firmware for MAX 1800</A></STRONG></LI> <UL> <LI><EM>From</EM>: Andre Beck <beck@ibh-dd.de></LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg10532.html">Subject: Re: (ASCEND) Lost Frame relay in software upgrade!</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg10530.html">Re: (ASCEND) multiple logins</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg10519.html">Re: (ASCEND) Firmware for MAX 1800</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg10533.html">Re: (ASCEND) Firmware for MAX 1800</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="maillist.html#10531"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd230.html#10531"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>