Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) mysterious pipeline reboot
No, I havent been doing anything weird at all on it, its just sitting there.
Since the last e-mail, the Pipe has been re-booting about every hour or so,
and losing the isdn lines about every 15-20 minutes. When it drops the lines,
it recovers very quickly, and is connected back up in seconds. If I check the
syslog to see, all it says is :
- Syslog Message: "<134>ASCEND: slot 2 port 2, Call Terminated"
- Syslog Message: "<134>ASCEND: slot 2 port 1, Call Terminated"
Now, I have called US West on this, due to the fact that we've had *severe*
problems with the isdn line in the past, namely it took them over 1 year to
get us a stable line. But since then, all has been fine with the line stayed
up for around 21 days at a timem, for the past couple of months. Considering
past history, my first guess is that a card went bad on US West's end in the
central office or some such. But, as usual, when I called, the first response
from them was that it could be a whole wide range of issues, from a bad jack,
to the router, to wiring on our end, so on and so forth.... So, im seeking to
try to eliminate all possible problems before speaking to them again on
Monday.
Could excessive crc errors, due to a bad isdn line cause the Pipe to reboot,
or to leak memory like you say? Or would a possible memory leak be due to
some other issue, not related to the line?
Thanks,
David
Jason Nealis wrote:
> Usually from my experience a Fatal Error 2 is a memory leak of some
> kind, If the box can't allocate any available memory it reboots, Are
> you doing anything weird on it by chance?
>
> Jason Nealis
> Director Internet Operations
> Network Access
> Erols Internet
>
> On Sat, 31 Jan 1998, David M. Way wrote:
>
> > Greetings,
> >
> > I had a Pipeline 50 mysteriously reboot on me about 10 minutes ago. Im
> > trying to figure out why it did, as nothing out of the ordinary was
> > going on, i.e.: not loading firmware, etc...
> > I went into diagnostic mode and typed fatal and received the following
> > message:
> >
> > > fatal
> > FATAL ERROR: Index: 2 Load: b.p50 Revision: 5.1Ap9
> > Location: 001a3c1c 00195f5c 0019621e 0019084a 001ac758 00119f50
> >
> > SYSTEM IS UP: Index: 100 Load: b.p50 Revision: 5.1Ap9
> >
> > Not knowing what that means, im hoping someone out there might. Also,
> > if the fatal message doesn't shed light, is there any reason it would
> > reboot out of the blue like that? Bad isdn line, so on and so
> > forth.....?
> >
> > thanks in advance,
> >
> > David Way
> > Operations Manager
> > Way Architects, P.C.
> >
> > ++ 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>
++ 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: