We've had a very similar problem with several of our 6000's. We've had this
problem at pop's with PRI as well as T1, and with software versions tbixkh
7.0.22, 7.2.0, and 8.0.3. I've found that the reason the call is refused is
that the when the ratio of bad to good calls gets too high, the max assumes
it's a problem with the modem card and therefore puts it on the 195 list to
be rebooted. Once it does this it, lists the card as unavailable and waits
for everyone on it to disconnect before rebooting the card.
The end result of this process is that while waiting for all the calls to
clear off the card, you have fewer modems than you thought. In our case,
this means you have more incoming lines than modems and so the max will
either refuse the call or it will route the call to HDLC drivers (in which
case, callers will hear digital tones and "show users" will list 56k or 64k
attempted connections).
If you want to see if this is what's happening, you can go to diagnostics
and type "avm" if your code <8.0 or "lanp modem" if your code is >8.0. These
commands will list all available, used, suspect and 195 (waiting for reset)
modems. This is usefull really only to see if the problem is occurring. You
can use the "fatal-history" command from diagnostics to see if the problem
haas occurred recently. It has the fatal log will list something like:
WARNING: Index: 195 Load: tbixkh.m60 Revision: 8.0.3
Date: 09/03/2000. Time: 13:00:34
Location: b022faf4 b022fe14 b022d894 b022df00 b022dfb4 b019a338
Well, that's all I know about it. I still don't know exactly what causes the
max put modems on the 195 list and I don't know if there's a way to prevent
this. I'm not entirely sure if it's an equipment or telco issue and I don't
know where to look from here. If anyone out there has any thought's on the
matter I would love to hear them. This is a problem that we've been
experiencing for a while a now and nobody seems to know what's going on so
any input at all would be appreciated.
Thanks.
Hope this helps some Steve.
---Dave Montgomery
IPA Network Technician
1-800-785-4091
-----Original Message-----
From: owner-ascend-users at max.bungi.com
[mailto:owner-ascend-users at max.bungi.com]On Behalf Of Steve Haavik
Sent: Thursday, September 07, 2000 6:45 AM
To: ascend-users at bungi.com
Subject: (ASCEND) MAX 6000 problems
Has anyone seen this or know what would cause it?
Sep 6 22:57:11 anne-gwa ASCEND: LPMOD: Slot 8 All Modems Down
We've been having a lot of trouble lately with this one site. I'm seeing
a large number of refused calls (with 2 to 4 modems in use) and strange
dialed numbers. The only thing I've found that will get it to start
answering calls again for more than a few hours is to reset the router.
I called Verizon about it and they took the PRI down for testing and of
course it worked for a few days after that, but now I 'm getting
complaints again. The router worked fine for a few months without
complaint and we have replaced it just to make sure. It's currently
running 7.2.4 tbaxkh.m60.
--
Steve Haavik
Sailor Operations Center
shaavik at soc.lib.md.us
Office: 410-396-5551
Cell: 410-371-3158
Pager: 410-379-1824
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request at bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request at bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>