JustAskingQuest's profile

JustAskingQuest

New Contributor

 • 

3 Messages

Closed

Connection lags/disconnects several times a day.

Have been having disconnections occur several times a day, didn't start till 11 days ago. Has now reached a point that is effecting my day to day.

Modem Logs look bad, but I'm not sure what any of it means, or what needs to be done.

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables
1 Locked QAM 256 1 783000000 Hz 6.8 dBmV 38.6 dB 662 2154
2 Locked QAM 256 2 789000000 Hz 7.0 dBmV 38.6 dB 378 2321
3 Locked QAM 256 3 795000000 Hz 6.9 dBmV 38.9 dB 257 2144
4 Locked QAM 256 4 801000000 Hz 6.9 dBmV 38.6 dB 334 2148
5 Locked QAM 256 5 807000000 Hz 7.1 dBmV 38.9 dB 326 1013
6 Locked QAM 256 6 813000000 Hz 7.1 dBmV 38.6 dB 443 884
7 Locked QAM 256 7 819000000 Hz 7.0 dBmV 38.9 dB 170 994
8 Locked QAM 256 8 825000000 Hz 7.0 dBmV 38.9 dB 315 962
9 Locked QAM 256 9 831000000 Hz 7.3 dBmV 38.6 dB 146 973
10 Locked QAM 256 10 837000000 Hz 7.5 dBmV 38.6 dB 71 77
11 Locked QAM 256 11 843000000 Hz 7.0 dBmV 38.6 dB 126 1947
12 Locked QAM 256 12 849000000 Hz 6.8 dBmV 38.6 dB 49 107
13 Locked QAM 256 13 855000000 Hz 6.1 dBmV 38.6 dB 120 1037
14 Locked QAM 256 14 861000000 Hz 5.6 dBmV 37.6 dB 217 1846
15 Locked QAM 256 15 867000000 Hz 5.3 dBmV 37.6 dB 126 1074
16 Locked QAM 256 16 873000000 Hz 5.3 dBmV 37.6 dB 192 1000
17 Locked QAM 256 17 879000000 Hz 5.8 dBmV 37.6 dB 266 971
18 Locked QAM 256 18 885000000 Hz 6.5 dBmV 37.6 dB 139 911
19 Locked QAM 256 19 891000000 Hz 8.3 dBmV 37.6 dB 157 57
20 Locked QAM 256 20 897000000 Hz 9.6 dBmV 38.6 dB 76 38
21 Locked QAM 256 21 903000000 Hz 8.5 dBmV 37.3 dB 76 36
22 Locked QAM 256 22 909000000 Hz 6.3 dBmV 37.3 dB 326 942
23 Locked QAM 256 23 915000000 Hz 4.4 dBmV 37.3 dB 303 920
24 Locked QAM 256 24 921000000 Hz 3.9 dBmV 37.3 dB 132 1068
25 Locked QAM 256 25 927000000 Hz 3.7 dBmV 37.3 dB 101 649
26 Locked QAM 256 26 933000000 Hz 4.0 dBmV 37.3 dB 60 54
27 Locked QAM 256 27 939000000 Hz 4.8 dBmV 36.9 dB 72 32
28 Locked QAM 256 28 945000000 Hz 5.4 dBmV 37.6 dB 76 699
29 Locked QAM 256 29 951000000 Hz 5.9 dBmV 37.6 dB 34 52
30 Locked QAM 256 30 957000000 Hz 6.4 dBmV 38.2 dB 55 673
31 Locked QAM 256 31 963000000 Hz 6.5 dBmV 38.6 dB 114 668
32 Locked QAM 256 32 969000000 Hz 6.5 dBmV 38.2 dB 317 33
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 6 2560 Ksym/sec 12900000 Hz 39.8 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 17700000 Hz 40.5 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 24100000 Hz 40.5 dBmV
4 Locked ATDMA 3 5120 Ksym/sec 30500000 Hz 41.5 dBmV
5 Locked ATDMA 4 5120 Ksym/sec 36900000 Hz 42.0 dBmV
6 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV

Discussions

 • 

Updated 

723

2

0

0

D

Dave9

Contributor III

 • 

251 Messages

Signal levels are good but the SNR seems to be lower than it should be for such strong signals.Could indicate noise getting in to the line. Tighten all connections and replace interior cables. Also post modem logs instead of just signals. The logs often are a better indicator of what's going on.

0

0

J

JustAskingQuest

New Contributor

 • 

3 Messages

Aug 08 2020 22:48:45 Critical (3) No Ranging Response received - T3 time-out
Aug 08 2020 22:48:45 Critical (3) No Ranging Response received - T3 time-out
Aug 08 2020 22:48:45 Critical (3) No Ranging Response received - T3 time-out
Aug 08 2020 22:50:25 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 08 2020 22:50:25 Critical (3) No Ranging Response received - T3 time-out
Aug 08 2020 22:52:05 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 08 2020 22:52:05 Critical (3) No Ranging Response received - T3 time-out
Aug 08 2020 22:53:45 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 08 2020 22:53:45 Critical (3) No Ranging Response received - T3 time-out
Aug 09 2020 13:23:42 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 09 2020 13:23:42 Critical (3) No Ranging Response received - T3 time-out
Aug 09 2020 13:25:21 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 09 2020 13:25:22 Critical (3) No Ranging Response received - T3 time-out
Aug 09 2020 19:10:10 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 09 2020 19:10:10 Critical (3) No Ranging Response received - T3 time-out
Aug 09 2020 19:11:48 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 09 2020 19:11:49 Critical (3) No Ranging Response received - T3 time-out
Aug 10 2020 19:23:10 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 10 2020 19:23:10 Critical (3) No Ranging Response received - T3 time-out
Aug 14 2020 05:43:39 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 14 2020 05:43:39 Critical (3) No Ranging Response received - T3 time-out
Aug 15 2020 19:17:22 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 15 2020 19:17:22 Critical (3) No Ranging Response received - T3 time-out
Aug 15 2020 19:32:41 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 15 2020 19:32:41 Critical (3) No Ranging Response received - T3 time-out
Aug 15 2020 19:34:01 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 15 2020 19:34:01 Critical (3) No Ranging Response received - T3 time-out
Aug 15 2020 19:35:21 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 15 2020 19:35:21 Critical (3) No Ranging Response received - T3 time-out
Aug 18 2020 02:11:08 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 18 2020 02:11:08 Critical (3) No Ranging Response received - T3 time-out
Aug 18 2020 03:02:43 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 18 2020 03:02:43 Critical (3) No Ranging Response received - T3 time-out
Aug 18 2020 19:07:49 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Aug 18 2020 19:07:49 Notice (6) TLV-11 - unrecognized OID
Aug 18 2020 23:56:39 Critical (3) No Ranging Response received - T3 time-out
Aug 20 2020 01:51:06 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 20 2020 01:51:06 Critical (3) No Ranging Response received - T3 time-out
Aug 20 2020 01:52:46 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Aug 20 2020 01:52:46 Critical (3) No Ranging Response received - T3 time-out
Aug 20 2020 06:59:51 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Aug 20 2020 06:59:51 Notice (6) TLV-11 - unrecognized OID

1

0

D
Dave9

Contributor III

 • 

251 Messages

Lots of T3 timeouts. Not a good sign. Check all cable connections. Connections should be tight. Replace indoor cables with new cables. Is the problem somewhat better than it was? There were a lot more errors around the 10th. But there should be no T3 timeouts at all. If all of your interior equipment and cables are good then you need a Cox tech to fix the problem.

Like

Reply

0

Related Content