Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Debugless MAX?
Thanks to all who replied
Turns out we had a telnet session open and in debug mode (there can only
be one debug session at any one time). Thanks to Dean Frye of Ascend
Australia for suggesting the Term Server command "show tcp con" to
identify the offender.
On Tue, 21 Jul 1998, Neale Banks wrote:
> Scenario:
>
> M4k-E1, 2 PRIs, 3 12-modem(S56), ISDN+modem dialups, 5.0Ap46
>
> All was relatively well (i.e. at least several weeks between reboots ;-)
> till we added a fourth K56 12-modem. Initially all was well, but after
> approx 24hrs we can't get into debug/diagnostics :-(
>
> After invoking the appropriate profile, the D=Diagnostics appears in the
> DO menu, but attempting to invoke it (from no less than three different
> terminals, including telnet and console) simply re-paints the menu screen.
> The Terminal Server appears unaffected.
>
> The catch of course is that it's pretty hard to diagnose this without
> access to those very useful debug commands ;-)
>
> Any ideas what's up? Better still, any suggestions on (a) if this is a
> sign of something evil brewing or (2) how to recover without a reboot?
>
> Thanks,
> Neale.
++ 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: