Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Disconnect-Cause 185
We ended up reloading the MAX image (tk.m40) to correct this problem. We
use trivial FTP to upload the image to the MAX, then issue the 'nvram'
diagnostic command which writes the image to non-volatile memory. After
writing the image to memory, the 'nvram' command 'resets' the MAX, and
the MAX goes through its self test routines. By 'reboot', are you
implying the 'reset' command, or do you mean a cold start (power down,
power up)? Thanks.
Kim W. Premuda
FastWave Internet Services
San Diego, CA
ascend@digistar.com wrote:
>
> On Sat, 23 Aug 1997, Kim Premuda wrote:
>
> > 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.
>
> 5.0Ai13 does the same for me. It's a fixable thing; you just have to
> reboot the MAX :( 5.0Ai13 definitely does NOT like talking to Ciscos...
>
> ++ 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>
Follow-Ups:
References: