(ASCEND) FE 1001 & 1006

[Joe Shaw <jshaw@insync.net>]

I kept getting these errors on 2 of my MAXEN on one segment of the
network.  I upgraded both to 5.0Ap48 and now one has worked fine since the
upgrade while the other continued to have problems.  I looked through the
archives of the list and only found one reference to these errors, but
the person was experiencing sporadic reboots.  Here we've seen it lose
it's ethernet and require a hard power cycle for it to come back.  So far
it happens every 1 to 3 days.

> fat
FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:26
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1006  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:26
        Location: b009bac4 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1012  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:32
        Location: b009d0bc b00a08e8 b00a0fe0 b0037fdc b0038890 b00581f4

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:32
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:33
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:33
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:33
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1006  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:33
        Location: b009bac4 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

OPERATOR RESET:  Index: 99  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:38
        MENU Reset from unknown in security profile 2.

FATAL ERROR:  Index: 1012  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:39
        Location: b009d0bc b00a08e8 b00a0fe0 b0037fdc b0038890 b00581f4

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:39
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:39
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:39
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1001  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:39
        Location: b009baa8 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

FATAL ERROR:  Index: 1006  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:00:39
        Location: b009bac4 b009d0dc b00a08e8 b00a0fe0 b0037fdc b0038890

SYSTEM IS UP:  Index: 100  Load: ti.m40 Revision: 5.0Ap48
        Date: 04/07/1998.       Time: 09:01:35


Joe Shaw - jshaw@insync.net
NetAdmin - Insync Internet Services
Fortue: 43rd Law of Computing: Anything that can go wr
	fortune: Segmentation violation -- Core dumped

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

---

• Prev by Date: (ASCEND) USR 33.6 Modems
• Next by Date: RE: (ASCEND) Arp routing
• Prev by thread: Re: (ASCEND) Ascend going mad ? (was: Stable code for Max 1800)
• Next by thread: (ASCEND) USR 33.6 Modems
• Index(es):
  • Main
  • Thread