Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) fatal error index 2
On Wed, Nov 26, 1997 at 02:05:17PM +1000, Virgil Braganza wrote:
> Any information on the following is appreciated;
>
> FATAL ERROR : Index : 2 Load: eik.m40 ....
If you're getting this error together with a reboot (and if it happens
quite regularly after around three days), you might be seeing the same
thing we are:
FATAL ERROR: Index: 2 Load: ebik.m40 Revision: 5.0Ap33
Date: 11/20/1997. Time: 14:42:54
Location: b019970c b01ed67c b01eca28 b01ecb78 b01ecfa0 b01eaa4c
SYSTEM IS UP: Index: 100 Load: ebik.m40 Revision: 5.0Ap33
Date: 11/20/1997. Time: 14:44:30
If you're running a fairly recent version (Ap27 or Ap33) your error
*might* be related to one of the following TR's mentioned in the
(now recalled) Ap34 Release:
TR 2804 MAX resets with FE 2 and Warning 175 every 3 days
Completed in: 5.0Ap34
On some software loads, if the MAX were running MAXDial (modem dialout) with
user authentication,
after a period of time the MAX would reset with Fatal Error (FE) 2.
TR 2398 The MAX units were resetting with an FE2.
Completed in: 5.0Ap34
MP+ calls which included IPX routing would cause the MAX to reset with Fatal
Erro (FE) 2.
If you're still running an older version you might want to check the
release notes of Ap33, which also mentions all the fixes in prior
patches.
--
Oliver J. Albrecht <olli@allcon.net>
AllCon GmbH Lise Meitner Str. 2 D-24941 Flensburg
EMail: allcon@allcon.net Tel: +49 461 9992-162 Fax: -165
++ 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: