Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Connections randomly disconnected on Max4000
You're stock answer from Ascend is going to be "Are you running the latest
version of software?" which you're obviously not. We had a few maxen with
stacking and OSPF working well under 5.0Ap4x, but had to upgrade to p48
for security fixes and then all our maxen started losing their ethernet
ports, sometimes 2-3 times a day. So, after having to come in at 4:30 in
the morning, I decided to upgrade to 6.0.4 (ti.m40). So far we've had no
instances of losing the ethernet (in diagnostics doing a fatal command in
5.0Ap46 and 48 showed about 6-8 Fatal Error 1001 and 1008's all at the
same memmory location all at the same time) and no outstanding problems as
of yet. I'm still watching them closeley, and I have noticed that instead
of having rock solid maxen with 3-11 day uptimes on average, we are back
to 4.6 and early 5.0 where we reboot every 1-2 days.
Joe Shaw - jshaw@insync.net
NetAdmin - Insync Internet Services
Fortune: 43rd Law of Computing: Anything that can go wr
fortune: Segmentation violation -- Core dumped
On Tue, 5 May 1998, Greg Harewood wrote:
>
> Hi all,
>
> I used to participate on this list more; since we got a reasonably
> stable MAX configuration, we have just left it in place for the
> past 12 months. Sorry if this is an FAQ:
>
> We are using 2 4000 series Ascends, stacking configured,
> on one LAN. They are running 5.0Ap1.
>
> Recently, (possibly with increased loading), we have been having far
> more problems with what appears to be periods of suspended communication.
> We are using IP over PPP, and TCP-Clear sessions, to a variety of clients.
>
> What happens is that data stops flowing; personally I see this after
> perhaps 1/2 hour logged in. My Mac (using OT) drops the line after 20
> seconds or so. Other people, using such as a p50 or linux, do not get
> a line drop and sometimes see communication return after a perhaps
> extended period of time.
>
> The uptime of the routers is quite long (several months). We are using
> 5 12modem cards, pre 56K. I have been loath to powercycle, because we
> tend to get a different problem where some PRI channels do not come back
> up after a reload.
>
> Disconnection codes for 1 day:
> Code Frequency
> 1 13 The event was not a disconnect.
> 11 922 The modem detected DCD, but became inactive.
> 12 5 The result codes could not be parsed.
> 24 50 The user exited normally from a raw TCP session.
> 25 1 The login process ended because the user failed..pass...
> 27 4 The login process ended because the user typed Ctrl-C.
> 35 3 ?
> 40 4 PPP LCP negotiation timed out while waiting for a response...
> 41 62 There was a failure to converge on PPP LCP negotiations.
> 43 2 PPP CHAP authentication failed.
> 45 760 The peer sent a PPP Terminate Request.
> 47 697 LCP closed because no NCPs were open.
> 49 6 LCP closed because it could not add any more channels to an MP
> 100 4 The session timed out because there was not activity on a PPP
> 185 1272 The call disconnected because the remote end hung up.
>
>
> I am planning to upgrade to a newer software revision - should I go for
> a late pl of 5 or should I go for 6.0.2? Is 6.0.2 stable with these old
> modems? Do my problems match any known TRs?
>
> Thanks for any help!
> Greg Harewood
> Kewill ElectricMail
> ++ 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: