Re: (ASCEND) Max reboot on 6.1.3

To: Edgar Scherer <esche@rz.uni-sb.de>
Subject: Re: (ASCEND) Max reboot on 6.1.3
From: "Oliver J. Albrecht" <oj@nexus.flensbone.net>
Date: Thu, 23 Jul 1998 23:28:32 +0200
Cc: ascend-users@bungi.com
In-Reply-To: <7b972e9a09d1@news.allcon.net> <f0f32841c9b7@news.allcon.net>
Sender: owner-ascend-users@max.bungi.com
User-Agent: tin/pre-1.4-980202 (UNIX) (Linux/2.0.33 (i586))

In article <f0f32841c9b7@news.allcon.net> you wrote:

>we have the same problem with the Max 4000 and the software 6.1.3:

>rip on, no ospf,
>> no stacking with 1 other box, analog and isdn dialups - only 2 pris...

>FATAL ERROR:  Index: 1  Load: feik.m40 Revision: 6.1.3
>        Date: 07/22/1998.       Time: 18:47:23
>        Location: b0106974 b01085f4 b0107e14 b0050e48 b00517a4 b006fb98

>SYSTEM IS UP:  Index: 100  Load: feik.m40 Revision: 6.1.3
>        Date: 07/22/1998.       Time: 18:49:25

We saw one of these this week, Index 1/reboot without apparent cause. After
checking mrtg stats, it appears to have been a DoS (probably a ping flood of 
some sort). The near 100% usage of our (otherwise never saturated) upstream 
connection was *very* obvious, judging from mrtg output. I haven't gotten the 
chance to take a deeper look into this one, but will if and when this happens 
again.

-- 
Oliver J. Albrecht <oj@nexus.flensbone.net>
++ 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) DNIS Auth/Filter
Next by Date: (ASCEND) Max 4048 PRI 7.0b0 code Fatal error
Prev by thread: Re: (ASCEND) Max reboot on 6.1.3
Next by thread: Re: (ASCEND) 4000 Series Underpowered?
Index(es):
- Main
- Thread