Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) tik.m40 working at all?
At 11:46 PM 12/17/97 -0500, David M. Ramsey wrote:
>Does *anyone* have a Max working reliably with tik.m40 ? I scanned
>the archives of this list and cannot find any mention of success.
It's a well known fact that people tend to talk louder when they are
complaining about things...
>We have a Max4048 that spontaneously and randomly reboots, sometimes with:
>
> FATAL ERROR: Index: 1 Load: tik.m40 Revision: 5.0Ap36
> Date: 12/17/1997. Time: 19:54:12
> Location: b017e5f4 b01804d0 b0180000 b007ab88 b007ac9c b004eb58
That's a new one on me. Have you bounced it off tech support yet to see if
they have experienced it? Did you do all of those fun 'fclear','fsave' etc.
When you did the upgrade? (Did you upgrade?).
>(different "Location" each time). Usually, though, it shows a 'normal'
>Index: 100 after its self-induced reboot. Everything _appears_
>to be working fine prior to the reboot -- ISDN calls succeed, K56
>calls succeed, OSPF works. Then suddenly, poof.
Has this happened before on any earlier releases ?
>Has anyone had reasonable uptime when using this machine with ISDN
>and K56 calls? I'll gladly back down to an older release (currently
>running 5.0Ap36) if that'll help.
>From what I've been reading, 5.0Ap36 seems to be the best so far - and we
just released 5.0Ap38 which should add more stability.
Kevin
++ 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: