This is what I see on all chassis when doing "sh mo" with 3.7 and k56 cards
sh mo
Mdm Port Status Speed Compression Protocol Calls Retrain Disconnect
--- ---- ------ ----- ----------- -------- ------ ------- ------------
M0 S2 ACTIVE 24000 V42BIS LAPM 24 0 V.42 FAILURE
M1 S14 ACTIVE 14400 V42BIS LAPM 24 0 CIRCUIT
DISCONNECT
M2 S24 ACTIVE 14400 V42BIS LAPM 36 0 LOST CARRIER
M3 S7 ACTIVE 33600 V42BIS LAPM 13 0 CIRCUIT
DISCONNECT
M4 S11 ACTIVE 14400 NONE DIRECT 31 2 CIRCUIT
DISCONNECT
M5 S13 ACTIVE 14400 NONE DIRECT 8 0 CIRCUIT
DISCONNECT
M6 S0 ACTIVE 28800 V42BIS LAPM 32 0 CIRCUIT
DISCONNECT
M7 S9 ACTIVE 33600 V42BIS LAPM 31 0 CIRCUIT
DISCONNECT
M8 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M9 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M10 S28 ACTIVE 33600 V42BIS LAPM 14 0 CIRCUIT
DISCONNECT
M11 S5 ACTIVE 31200 V42BIS LAPM 28 0 CIRCUIT
DISCONNECT
M12 S41 ACTIVE 33600 V42BIS LAPM 40 0 CIRCUIT
DISCONNECT
M13 S17 ACTIVE 28800 V42BIS LAPM 37 0 LAPM DISCONNECT
M14 S4 ACTIVE 31200 V42BIS LAPM 16 2 CIRCUIT
DISCONNECT
M15 S19 ACTIVE 33600 V42BIS LAPM 26 0 LAPM DISCONNECT
M16 S3 ACTIVE 31200 V42BIS LAPM 16 0 CIRCUIT
DISCONNECT
M17 S10 ACTIVE 33600 NONE MNP 23 0 V.42 FAILURE
M18 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M19 ADMIN UNKNWN NONE NONE 0 0 NORMAL
-- Press Return for More --
M20 S6 ACTIVE 28800 V42BIS LAPM 21 0 CIRCUIT
DISCONNECT
M21 S27 ACTIVE 14400 V42BIS LAPM 27 0 CIRCUIT
DISCONNECT
M22 S44 ACTIVE 4800 NONE LAPM 35 0 CIRCUIT
DISCONNECT
M23 S25 ACTIVE 33600 V42BIS LAPM 45 0 CIRCUIT
DISCONNECT
M24 S16 ACTIVE 33600 V42BIS LAPM 28 0 CIRCUIT
DISCONNECT
M25 S20 ACTIVE 28800 V42BIS LAPM 31 0 LAPM DISCONNECT
M26 S33 ACTIVE 31200 V42BIS LAPM 30 0 V.42 FAILURE
M27 S26 CONNECT UNKNWN NONE NONE 18 0 LAPM DISCONNECT
M28 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M29 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M30 S1 ACTIVE 28800 V42BIS LAPM 40 0 CIRCUIT
DISCONNECT
M31 S35 ACTIVE 28800 V42BIS LAPM 29 0 LAPM DISCONNECT
M32 S30 ACTIVE 33600 V42BIS LAPM 20 0 LOST CARRIER
M33 READY UNKNWN NONE NONE 30 2 CIRCUIT
DISCONNECT
M34 S36 ACTIVE 33600 V42BIS LAPM 26 0 LAPM RETRY
LIMIT
M35 S39 ACTIVE 33600 V42BIS LAPM 18 0 LAPM DISCONNECT
M36 S18 ACTIVE 28800 V42BIS LAPM 25 0 CIRCUIT
DISCONNECT
M37 S43 ACTIVE 9600 NONE LAPM 25 0 CIRCUIT
DISCONNECT
M38 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M39 ADMIN UNKNWN NONE NONE 0 0 NORMAL
-- Press Return for More --
M40 S38 ACTIVE 31200 V42BIS LAPM 29 0 CIRCUIT
DISCONNECT
M41 S42 ACTIVE 33600 V42BIS LAPM 28 0 LAPM RETRY
LIMIT
M42 S22 ACTIVE 31200 V42BIS LAPM 18 0 LAPM DISCONNECT
M43 READY UNKNWN NONE NONE 33 1 CIRCUIT
DISCONNECT
M44 S32 ACTIVE 28800 V42BIS LAPM 23 0 LAPM DISCONNECT
M45 READY UNKNWN NONE NONE 17 0 CIRCUIT
DISCONNECT
M46 S31 ACTIVE 31200 V42BIS LAPM 17 0 CIRCUIT
DISCONNECT
M47 S21 ACTIVE 12000 V42BIS LAPM 21 0 LAPM RETRY
LIMIT
M48 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M49 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M50 S37 ACTIVE 31200 V42BIS LAPM 22 0 CIRCUIT
DISCONNECT
M51 S8 ACTIVE 31200 V42BIS LAPM 19 5 CIRCUIT
DISCONNECT
M52 READY UNKNWN NONE NONE 12 0 CIRCUIT
DISCONNECT
M53 READY UNKNWN NONE NONE 21 0 CIRCUIT
DISCONNECT
M54 S15 ACTIVE 16800 V42BIS LAPM 16 0 CIRCUIT
DISCONNECT
M55 S40 ACTIVE 28800 V42BIS LAPM 24 0 LAPM RETRY
LIMIT
M56 S12 ACTIVE 33600 V42BIS LAPM 20 0 LOST CARRIER
M57 READY UNKNWN NONE NONE 6 3 CIRCUIT
DISCONNECT
M58 ADMIN UNKNWN NONE NONE 0 0 NORMAL
M59 ADMIN UNKNWN NONE NONE 0 0 NORMAL
<snip>
> Can anyone verify this with ComOS 3.7 and the *OLD* modem cards?
Customer
> calls, seems to be working just fine. Then data stops transferring. If
> you try to ping the customer, or check for activity, the line does
> nothing. The idle timer doesn't even reset.
>
> After about a minute of the port locking, the call is dropped. RADIUS
> shows "User Request", but the disconnect log shows "User Request - Call
> Circuit Disconnect" ... I don't know if the old cards will show this.
> Someone from Livingston can verify that.
>
> I've been listening to the problems, and it seems quite a few people are
> having them. If people with the old cards are *ALSO* having the problem,
> perhaps Livingston can look elsewhere. Since the v.42 problem has a
"fix"
> of sorts that allows the customers to stay online, I think this other
> problem is more serious. There is *NO* fix to this port locking problem.
>
> Oh, also, occasionally I see "Port sx stopped too long - flushing packet
> queue" ... This is only on the ports that have locked.
>
> Jaime Bozza
> Nucleus Communications, Inc.
>
Chris Evoy
HyperNet
cevoy@lonet.ca
http://www.lonet.ca