Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 5.0ap27????
At 10:55 AM 9/29/97 -0700, Matt Holdrege wrote:
>At 01:38 PM 9/29/97 -0400, Rick Wagner wrote:
>>Has the HDLC problem from Ap16, been corrected in Ap27?
>
>What HDLC problem?
TR#2554. Open, high-priority in Engineering.
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>
From owner-ascend-users@max.bungi.com Mon Sep 29 17:22:41 1997
Received: from max.bungi.com (max.bungi.com [207.126.97.7]) by warrior.real-time.com (8.8.5/8.7.3) with ESMTP id RAA00463; Mon, 29 Sep 1997 17:22:38 -0500 (CDT)
Received: (from majordom@localhost)
by max.bungi.com (8.8.7/8.8.7) id NAA27399
for ascend-users-outgoing; Mon, 29 Sep 1997 13:21:36 -0700 (PDT)
X-Authentication-Warning: max.bungi.com: majordom set sender to owner-ascend-users using -f
Received: from daver.bungi.com (daver.bungi.com [207.126.97.2])
by max.bungi.com (8.8.7/8.8.7) with ESMTP id NAA27394
for <ascend-users@max.bungi.com>; Mon, 29 Sep 1997 13:21:31 -0700 (PDT)
Received: from drawbridge.ascend.com(really [198.4.92.1]) by daver.bungi.com
via sendmail with esmtp
id <m0xFmJu-0000XZC@daver.bungi.com>
for <ascend-users@bungi.com>; Mon, 29 Sep 1997 13:21:30 -0700 (PDT)
(Smail-3.2.0.94 1997-Apr-22 #8 built 1997-Jun-19)
Received: from spud.ascend.com (fw-ext.ascend.com [198.4.92.5])
by drawbridge.ascend.com (8.6.12/8.6.12) with ESMTP
id NAA10632 for <ascend-users@bungi.com>; Mon, 29 Sep 1997 13:19:31 -0700
Received: from ascend.com by ascend.com with SMTP
id NAA21823 for <ascend-users@bungi.com>; Mon, 29 Sep 1997 13:19:29 -0700
Message-Id: <3.0.1.32.19970929125959.00a6f828@mktg_srv.ascend.com>
X-Sender: kevin@mktg_srv.ascend.com
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Mon, 29 Sep 1997 12:59:59 -0700
To: Ascend User-Group <ascend-users@bungi.com>
From: Kevin Smith <kevin@ascend.com>
Subject: Re: (ASCEND) Can't telnet anymore
In-Reply-To: <Pine.LNX.3.96.970920084726.302D-100000@fell-light>
References: <Pine.OSF.3.93.970919100742.5041C-100000@singapura.singnet.com.sg>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ascend-users@max.bungi.com
Precedence: bulk
At 08:48 AM 9/20/97 +1200, Josh Bailey wrote:
>
>On Fri, 19 Sep 1997, Sajari wrote:
>
>> I have this problem with one of my Max4000.
>> After sometimes i'm not able to telnet in anymore.
>> The only solution is to load again the ascend firmware.
>> Currently i'm using 5.0Ap13.
>
>Hmmm... We use p13 - 'cos it's pretty stable compared to recent
>releases... :)
>
>We use telnet all the time to 52 Maxes - no problem telnetting, even after
>months of uptime.
Sometimes, people telnet in and leave the session hanging. There are limits
to the number of telnet sessions that the various units will accept, so you
may be hitting that. Also, there is a 2-minute "wait" period after a session
has been "killed" during which the socket is kept open (I believe it's per
the RFC....I just don't recall the exact details), so maybe if you wait for
a couple of minutes and try again.
Reloading the firmware seems to be way-overkill....have you at least tried
resetting the box ?
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>
Follow-Ups:
References: