Frequent intermittent disconnects through the day lasting from just a few seconds to a few minutes. Incredibly frustrating.
Date Time |
Event ID |
Event Level |
Description |
02/03/2022 22:19 |
82000500 |
3 |
"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 22:07 |
2436694061 |
5 |
"Dynamic Range Window violation" |
02/03/2022 22:07 |
82001200 |
5 |
"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 22:07 |
2436694061 |
5 |
"Dynamic Range Window violation" |
02/03/2022 22:07 |
82001200 |
5 |
"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 22:03 |
2436694061 |
5 |
"Dynamic Range Window violation" |
02/03/2022 22:03 |
82001200 |
5 |
"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 21:45 |
2436694061 |
5 |
"Dynamic Range Window violation" |
02/03/2022 21:45 |
82001200 |
5 |
"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 21:45 |
2436694061 |
5 |
"Dynamic Range Window violation" |
02/03/2022 21:45 |
82001100 |
5 |
"RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 19:53 |
74010100 |
6 |
"CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 19:52 |
74010100 |
6 |
"CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 19:25 |
82000500 |
3 |
"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 19:24 |
2436694061 |
5 |
"Dynamic Range Window violation" |
02/03/2022 19:24 |
82001200 |
5 |
"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 19:24 |
2436694061 |
5 |
"Dynamic Range Window violation" |
02/03/2022 19:24 |
82001200 |
5 |
"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
02/03/2022 19:22 |
82000500 |
3 |
"Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.1;" |
Downstream Bonded Channels |
Channel ID |
Lock Status |
Modulation |
Frequency |
Power |
SNR/MER |
Corrected |
Uncorrectables |
17 |
Locked |
QAM256 |
549000000 Hz |
1.1 dBmV |
40.6 dB |
0 |
0 |
1 |
Locked |
QAM256 |
447000000 Hz |
3.6 dBmV |
42.0 dB |
0 |
0 |
2 |
Locked |
QAM256 |
453000000 Hz |
3.0 dBmV |
41.7 dB |
0 |
0 |
3 |
Locked |
QAM256 |
459000000 Hz |
2.5 dBmV |
41.5 dB |
0 |
0 |
4 |
Locked |
QAM256 |
465000000 Hz |
2.4 dBmV |
41.4 dB |
0 |
0 |
5 |
Locked |
QAM256 |
471000000 Hz |
2.4 dBmV |
41.3 dB |
0 |
0 |
6 |
Locked |
QAM256 |
477000000 Hz |
2.8 dBmV |
41.2 dB |
0 |
0 |
7 |
Locked |
QAM256 |
483000000 Hz |
2.0 dBmV |
41.1 dB |
0 |
0 |
8 |
Locked |
QAM256 |
489000000 Hz |
1.3 dBmV |
41.0 dB |
0 |
0 |
9 |
Locked |
QAM256 |
495000000 Hz |
2.4 dBmV |
41.0 dB |
0 |
0 |
10 |
Locked |
QAM256 |
507000000 Hz |
2.4 dBmV |
41.1 dB |
0 |
0 |
11 |
Locked |
QAM256 |
513000000 Hz |
2.9 dBmV |
41.4 dB |
0 |
0 |
12 |
Locked |
QAM256 |
519000000 Hz |
2.2 dBmV |
41.2 dB |
0 |
0 |
13 |
Locked |
QAM256 |
525000000 Hz |
2.9 dBmV |
41.3 dB |
0 |
0 |
14 |
Locked |
QAM256 |
531000000 Hz |
2.4 dBmV |
41.3 dB |
0 |
0 |
15 |
Locked |
QAM256 |
537000000 Hz |
2.3 dBmV |
41.0 dB |
0 |
0 |
16 |
Locked |
QAM256 |
543000000 Hz |
2.2 dBmV |
40.9 dB |
0 |
0 |
18 |
Locked |
QAM256 |
555000000 Hz |
1.1 dBmV |
40.6 dB |
0 |
0 |
19 |
Locked |
QAM256 |
561000000 Hz |
1.8 dBmV |
40.8 dB |
0 |
0 |
20 |
Locked |
QAM256 |
567000000 Hz |
2.8 dBmV |
41.1 dB |
0 |
0 |
21 |
Locked |
QAM256 |
573000000 Hz |
3.4 dBmV |
41.3 dB |
0 |
0 |
22 |
Locked |
QAM256 |
579000000 Hz |
3.1 dBmV |
41.2 dB |
24 |
0 |
23 |
Locked |
QAM256 |
585000000 Hz |
1.9 dBmV |
40.8 dB |
26 |
51 |
24 |
Locked |
QAM256 |
591000000 Hz |
1.6 dBmV |
40.5 dB |
8 |
43 |
25 |
Locked |
QAM256 |
597000000 Hz |
1.5 dBmV |
40.5 dB |
18 |
83 |
26 |
Locked |
QAM256 |
603000000 Hz |
1.7 dBmV |
40.6 dB |
40 |
34 |
27 |
Locked |
QAM256 |
609000000 Hz |
1.3 dBmV |
40.4 dB |
13 |
28 |
28 |
Locked |
QAM256 |
615000000 Hz |
0.9 dBmV |
40.5 dB |
87 |
63 |
29 |
Locked |
QAM256 |
621000000 Hz |
1.0 dBmV |
39.9 dB |
89 |
60 |
30 |
Locked |
QAM256 |
627000000 Hz |
0.9 dBmV |
39.2 dB |
71 |
262 |
31 |
Locked |
QAM256 |
633000000 Hz |
0.0 dBmV |
39.1 dB |
118 |
516 |
32 |
Locked |
QAM256 |
639000000 Hz |
0.9 dBmV |
39.6 dB |
104 |
484 |
159 |
Locked |
Other |
762000000 Hz |
4.4 dBmV |
39.2 dB |
3406377030 |
354 |
Upstream Bonded Channels |
Channel |
Channel ID |
Lock Status |
US Channel Type |
Frequency |
Width |
Power |
1 |
1 |
Locked |
SC-QAM Upstream |
35600000 Hz |
6400000 Hz |
38.0 dBmV |
2 |
2 |
Locked |
SC-QAM Upstream |
29200000 Hz |
6400000 Hz |
39.0 dBmV |
3 |
3 |
Locked |
SC-QAM Upstream |
22800000 Hz |
6400000 Hz |
39.0 dBmV |
4 |
4 |
Locked |
SC-QAM Upstream |
16400000 Hz |
6400000 Hz |
39.0 dBmV |
5 |
5 |
Locked |
SC-QAM Upstream |
39600000 Hz |
1600000 Hz |
39.0 dBmV |
Information |
Standard Specification Compliant |
Docsis 3.1 |
Hardware Version |
6 |
Software Version |
AB01.02.053.05_051921_193.0A.NSH |
EG
Expert
•
110.2K Messages
3 years ago
Is there a router ? WiFi connection in the mix here ?
If so, for a test, does a computer that is hardwired directly to the cable modem have the same problem ?
With this test, we are trying to isolate this down to being either a WiFi-only problem or a problem with the general connection to the Comcast system which would of course affect both. It's a good first step of troubleshooting before proceeding any further.
0
0
ewp15
Visitor
•
8 Messages
3 years ago
Hey EG
It's affecting all devices, hardwired and wireless. There's a router, but I've tested hardwired directly into the modem as well and the issue persists. Entire run from modem to pole outside the house is relatively new and was verified as good by various techs over the last couple years when they've been out here for other things. No splitters.
It's an issue that occurs for a couple days and then is fine for a month, give or take, before happening again for sometimes up to a week. Sometimes the drops are barely noticeable but yesterday was particularly bad. When it's less bad you won't notice it with things that buffer substantially like Netflix, but it still makes conference calls or working from home or gaming impossible. When it's bad like yesterday the disconnects can last longer than a few minutes and occur much more often.
I think my numbers in the tables above look pretty good from my limited knowledge, which tells me that it's not the result of a continually degraded connection. The majority of the time, when these blips aren't happening or are mild enough, the connection is otherwise solid. It feels like something is going on or fluctuating between the pole and the Comcast substation (unsure what the official name is) that I'm connected to, or some parameter at the station itself is out of wack and needs to be adjusted, but obviously there's nothing I can do about that.
Thanks
(edited)
0
0
EG
Expert
•
110.2K Messages
3 years ago
O/k so even though the signal stats looked good at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) / an upstream channel-return path impairment somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
2
0
ewp15
Visitor
•
8 Messages
3 years ago
Thanks, I appreciate it!
1
0