PM3 'stuck'

Ron Tapia (tapia@nmia.com)
Wed, 9 Jul 1997 22:19:07 -0600 (MDT)

Equipment:

PM3
3 '10 port' cards
CT1, E&M immediate start, B8ZS, ESF

Calling in with a Cardinal 28.8

Ticket: 40016 (not that I've been called or anything)

I've seen a lot of lost carriers with 3.5.1b20.

In addition, I've been seen a problem where a connection will hang and
either unhang or die due to a loss of carrier.

The hangs seem to be associated with retrains (maybe renegotiations). These
hangs can last many minutes (recollection, I haven't timed anything yet) and
can seem permanent (i.e., before I thought that the connection was dead and
I'd hang up). It's just now what I've realized that my connections can
unhang.

It seems like my PM3 is retraining/renegotiating much too often for
usability (or it's taking to long to do one or the other). Is it possible
that 3.5.1b20 is a little too sensitive to line noise (for US West
territory)?

Just in the course of writing this message I've experienced several hangs
and two hangs followed by disconnects. I'm beginning to favor the
hypothesis that the hangs and disconnects are related and are both
related to the sensitivity of the 3.5.1b20 code to line noise.
Is there a better explanation?

Here's a full description for those interested. I'm hoping that it will
help others that see this problem know what to look for. If other info
would be of help, please let me know.

My PPP session was "hung" it was on m0. I was connected on another phone
line and on the PM3 in question. Here is "show m0":

==========================================================
dpm1> show m0
State: ACTIVE
Active Port: S0
Transmit Rate: 28800
Receive Rate: 26400
Connection Type: LAPM/V42BIS
Chars Sent: 70837038
Chars Received: 10681725
Retrains: 1
Renegotiations: 0

Total Calls: 197
Modem Detects: 192
Good Connects: 170

Connection Failures
No Modulation: 13
No Protocol: 13
Not Operational: 9
Total Failed: 22

Session Terminations
Lost Carrier: 0
Normal Disconnect: 169
==========================================================

I was typing into a telnet window and I could see the "send" light on my
modem blinking, but I never received responses. This lasted about a
minute. Suddenly, my connection came back, my characters were echoed in
my telnet session and "show m0" gave:

==========================================================
dpm1> show m0
State: ACTIVE
Active Port: S0
Transmit Rate: 21600
Receive Rate: 21600
Connection Type: LAPM/V42BIS
Chars Sent: 70855214
Chars Received: 10683091
Retrains: 2
Renegotiations: 0

Total Calls: 197
Modem Detects: 192
Good Connects: 170

Connection Failures
No Modulation: 13
No Protocol: 13
Not Operational: 9
Total Failed: 22
==========================================================

After only 1 other noticable hang "show m0" gives:

==========================================================
dpm1> show m0
State: ACTIVE
Active Port: S0
Transmit Rate: 26400
Receive Rate: 26400
Connection Type: LAPM/V42BIS
Chars Sent: 71057433
Chars Received: 10882282
Retrains: 3
Renegotiations: 8

Total Calls: 197
Modem Detects: 192
Good Connects: 170

Connection Failures
No Modulation: 13
No Protocol: 13
Not Operational: 9
Total Failed: 22

Session Terminations
Lost Carrier: 0
Normal Disconnect: 169
==========================================================

As I was composing this, I saw another hang, "show m0" gave:

==========================================================
dpm1> show m0
State: READY
Chars Sent: 71101167
Chars Received: 10908630
Retrains: 4
Renegotiations: 8

Total Calls: 197
Modem Detects: 192
Good Connects: 170

Connection Failures
No Modulation: 13
No Protocol: 13
Not Operational: 9
Total Failed: 22

Session Terminations
Lost Carrier: 0
Normal Disconnect: 170
==========================================================

This time, instead of "unhanging", I lost carrier. I reconnected and got
the same modem.

Here is "show modems":

==========================================================
dpm1> show mod
Mdm Port Status Speed Compression Protocol Calls Retrain Disconnect
--- ---- ------ ----- ----------- -------- ------ ------- ------------
M0 S0 ACTIVE 28800 V42BIS LAPM 171 0 LOST CARRIER
M1 S1 ACTIVE 26400 V42BIS LAPM 292 0 NORMAL
M2 S2 ACTIVE 26400 V42BIS LAPM 268 0 LOST CARRIER
M3 READY UNKNWN NONE NONE 290 0 NORMAL
M4 S4 ACTIVE 21600 V42BIS LAPM 212 0 LOST CARRIER
M5 S5 ACTIVE 28800 V42BIS LAPM 185 0 LOST CARRIER
M6 READY UNKNWN NONE NONE 149 1 NORMAL
M7 READY UNKNWN NONE NONE 88 0 LOST CARRIER
M8 READY UNKNWN NONE NONE 62 0 LOST CARRIER
==========================================================

It shows that M0 last disconnected because of a lost carrier.

While composing this, I saw another hang followed by a loss of carrier.

Thanks for your time,

Ron

--
Hagbard@LambdaMOO   % It's not a clique, it's a cabal.
Ron@JaysHouseMOO    % ...and there is no cabal.
Ron@MediaMOO        % 
<A HREF="http://www.nmia.com/~tapia/">My home page</A>