je-7595's profile

New Poster

 • 

1 Message

Fri, Aug 21, 2020 7:00 AM

Several disconnects and millions of uncorrectables

I can go several hours without disconnects, then suddenly my internet will disconnect 5-10 times in an hour. It's been this way for the last month. The channel SNR/Power look's the same way it has for the last year, I don't know why I'm having problems all of a sudden. Is it possible for someone to check my node without having to come in my house?

 

Downstream Bonded Channels  
ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25613525000000 Hz-1.1 dBmV45.0 dB386600007334244211083285
2LockedQAM2561453000000 Hz-2.9 dBmV43.9 dB18292311436935363017703
3LockedQAM2562459000000 Hz-1.8 dBmV44.5 dB19594081971213765084308
4LockedQAM2563465000000 Hz-2.4 dBmV44.4 dB233226471960438575682711
5LockedQAM2564471000000 Hz-2.3 dBmV44.4 dB232904470758324284184780
6LockedQAM2565477000000 Hz-2.5 dBmV44.2 dB210861573251857392840864
7LockedQAM2566483000000 Hz-1.5 dBmV44.7 dB270484500151011552035712
8LockedQAM2567489000000 Hz-2.5 dBmV44.3 dB173357609236295061675036
9LockedQAM2568495000000 Hz-1.8 dBmV44.7 dB302264639725176651577693
10LockedQAM2569501000000 Hz-1.2 dBmV44.8 dB255293774421677971288210
11LockedQAM25610507000000 Hz-1.5 dBmV44.7 dB99136190521566161863286
12LockedQAM25611513000000 Hz-1.3 dBmV44.6 dB389866572810970621061204
13LockedQAM25612519000000 Hz-0.8 dBmV45.0 dB394554423611308821141280
14LockedQAM25614531000000 Hz-1.9 dBmV44.5 dB252609192014138751491249
15LockedQAM25615537000000 Hz-1.3 dBmV44.8 dB213540129413176281070000
16LockedQAM25616543000000 Hz-2.0 dBmV44.5 dB252435503317775921454470
17LockedQAM25617549000000 Hz-3.0 dBmV44.0 dB169135818521074611448976
18LockedQAM25618555000000 Hz-2.3 dBmV44.4 dB170163752728064121816525
19LockedQAM25619561000000 Hz-1.8 dBmV44.3 dB174859867627616781912947
20LockedQAM25620567000000 Hz-2.1 dBmV44.5 dB175477785225113061778379
21LockedQAM25621573000000 Hz-2.9 dBmV43.9 dB304430451319921031547105
22LockedQAM25622579000000 Hz-1.8 dBmV44.4 dB312609883316605331420120
23LockedQAM25623585000000 Hz-3.2 dBmV43.5 dB215238673933710904740675
24LockedQAM25624591000000 Hz-2.3 dBmV43.9 dB305740481325304252204868
25LockedQAM25625597000000 Hz-2.7 dBmV43.2 dB295607829523765831747658
26LockedQAM25626603000000 Hz-3.0 dBmV43.1 dB309838048623389051788013
27LockedQAM25627609000000 Hz-4.1 dBmV42.9 dB21265364720561381781451
28LockedQAM25628615000000 Hz-2.5 dBmV43.8 dB309185403329163774781082
29LockedQAM25630621000000 Hz-2.8 dBmV43.5 dB307236396626575392625104
30LockedQAM25631627000000 Hz-3.9 dBmV42.8 dB179257567119485482210221
31LockedQAM25632633000000 Hz-3.4 dBmV43.1 dB6212854819755361992788
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
  

  
Upstream Bonded Channels  
ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA6136500000 Hz53.8 dBmV
2LockedATDMA6230100000 Hz53.8 dBmV
3LockedATDMA6323700000 Hz53.8 dBmV
4LockedATDMA6417300000 Hz53.3 dBmV
5Not LockedUnknown00 Hz0.0 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV
  

  
Downstream OFDM Channels  
2020-08-21, 09:21:35Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:16:10Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:16:04Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:15:43Critical (3)No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:14:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:14:23Warning (5)MDD message timeout;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:14:18Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:14:17Warning (5)MDD message timeout;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:14:13Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:14:06Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:14:02Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:13:48Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:13:21Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:13:16Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:11:51Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:11:28Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:11:19Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:11:06Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:11:00Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:10:14Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:10:13Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:10:06Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:09:20Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:09:11Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:09:05Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:08:20Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:08:20Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:08:03Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:07:58Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:07:34Notice (6)CM-STATUS message sent. Event Type Code: 20; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:06:45Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:06:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:04:12Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:04:06Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:04:02Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:03:57Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:03:43Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:03:32Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:02:47Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;
2020-08-21, 09:02:40Warning (5)MDD message timeout;CM-MAC=cc:40:d0:26:f3:b8;CMTS-MAC=00:01:5c:72:42:71;CM-QOS=1.1;CM-VER=3.1;

Responses

EG

Expert

 • 

86.1K Messages

8 m ago

The upstream power is too high / out of spec and it may be intermittently fluctuating even higher. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!tick

New to the Community?

Start Here