Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) Disconnect-Cause 185

Ivan Lum, Technical Support at Ascend, told us that 5.0Ap20 had the
latest Rockwell code (version 1.054) which addresses the sudden
disconnect problems with K56flex modems. Unfortunately, since upgrading
our MAX to 5.0Ap20 (see below), our customers are still reporting that
they are being disconnected after 20-23 minutes of connect time. We
verified our customer complaints by implementing a huge FTP file
transfer with a Zoom K56flex modem; during our three attempts, we were
abruptly disconnected within the 20-23 minutes time frame as well. The
other users reporting this problem are K56flex modem users, not USR X2
modems. One user has a Zoom K56flex external modem while another user
has an external Motorola Modem Surfer. Neither user could confirm what
version of K56flex software they are using and are in the process of
getting updates. So, the problem could be their modem's software and not
the MAX 5.0Ap20 (at least, at this point).

We, too, like other MAX users are beginning to hear from 14,400 modem
users. Their complaint is that they cannot make any connections. After
investigating, we found that they are being connected (that is, the MAX
answers), but authentication seems to either not happen at all, or it
will take 4-5 minutes to get a LAN session up message.

Reloading the software was performed using a TFTP server to upload the
image (5.0Ap20) to the MAX, then performing the 'nvram' command. During
the upload process, a message appears denoting a 'thin' load. After
issuing the 'nvram' command, the MAX performed a double reset and went
on-line. Whether this really fixed the problem is questionable, since
customers are still reporting sudden disconnects. We are working with
them to obtain modem software upgrades so that we can performs the tests
again.

Kim W. Premuda
FastWave Internet Services
San Diego, CA


Kevin Smith wrote:
> 
> At 11:44 AM 8/23/97 -0700, Kim Premuda wrote:
> >Our 56Kfelx customers were randomly getting disconnected under 5.0Ap16,
> >however, the time involved varied from 5-10 minutes, minimum, to 25-30
> >mintutes, maximum. Ascend Technical Support told us to upgrade to
> >5.0Ap20 to correct this problem, which we did. The upgrade has only been
> >running two days, so it's too early to tell if that fixed things...but,
> >we haven't heard any customer complaints either.
> 
> Were many of them USR Sportster users ?
> 
> >Since the upgrade, however, we have been getting yellow and red alarms
> >on our T1/PRI with occassional 1s (keep alive) which we NEVER got
> >before. PacBell has tested our T1/PRI line twice in the last two days
> >and cannot find anything. We cannot say for certain the Ap20 is the
> >culprit, but it does appear coincidental that the T1/PRI problems
> >started showing up 4 hours after installing the software upgrade.
> 
> I see in a later posting, that you fixed this by re-loading the software?
> Can you give any more details, so that we can understand what re-loading
> the software fixed ? (Maybe it was the NVRAM command....?).
> 
> 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: