Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) Re: Problems with Modems on the suspect list
On Thu, 9 Apr 1998, Cyril Jaouich wrote:
> > avm
> Modems on free list:
> Modem 3:8, 2059 calls, 101 bad, last 32 calls = fffffff7 dir=3
> Modem 3:9, 1911 calls, 74 bad, last 32 calls = ffffff7f dir=3
> Modems on suspect list:
> Modem 5:13, 1356 calls, 73 bad, last 32 calls = ffdfff00 dir=3
>
> Why is the modem on 5:13 stuck at 1356 calls while every other
> modem on that box is at ~2000 calls?
Also these modems are part of a hunt group, the machine which has
does modem has the 7th PRI & 8th PRI in a 14 PRI dial-up pool. Which is
running at 90% capacity at night. According to the debug docs, if all
non-suspect modems are busy, the suspect modem should be used to establish
a connection, expect that it never receives a call. According to my
syslog, the modem hasn't taken a call in over 14 days...
> Another machine:
>
> > avm
> Modems on free list:
> Modem 5:6, 293 calls, 10 bad, last 32 calls = ffefffff dir=3
> Modem 3:8, 276 calls, 14 bad, last 32 calls = ffffffff dir=3
> Modems on suspect list:
> Modem 5:1, 4 calls, 4 bad, last 4 calls = 00000000 dir=3
> Modem 5:2, 4 calls, 4 bad, last 4 calls = 00000000 dir=3
>
> Same here, this is quite bizzare. We have had some problems with
> channels staying free on the machine, I think this problem might be
> related to this.
>
> I am running 5.0Ap36 (tk.m40) on Max4004/48 with Rev. F k56 cards.
> I know of:
>
> TR 2996 AVM diagnostic command reports disabled modems (Part one)
> Completed in: 5.0Ap44.
>
>
> Has someone else ran into the same problems?
Sorry for replying to my own message.
Cyril Jaouich [CJ837]
---------------------
ACC DATA OPERATIONS EASTERN CANADA/US
-------------------------------------
++ 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: