Community Forum

Re: Intermittent connection drops

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

New Poster

Re: Intermittent connection drops

I'm having a similar problem where every the gateway connection is dropped every 5minutes for about 20-30 seconds, stopping my ability to use any realtime voice or video application.  Can you please point me in the right direction? 

 

Here's the event log and downstream/upstream stats from my NetGear CM1000:

 
 
 
 
Time Priority Description
2018-05-01, 07:55:41 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:55:31 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:55:24 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:55:24 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:55:19 Warning (5) MDD message timeout;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:53:40 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:53:34 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:53:30 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:53:22 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:53:09 Warning (5) MDD message timeout;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:51:28 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:51:19 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:51:11 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:51:02 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:51:00 Warning (5) MDD message timeout;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:49:17 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:49:01 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:49:00 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:48:53 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:48:49 Warning (5) MDD message timeout;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:47:07 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:47:06 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:47:05 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:46:55 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:46:39 Warning (5) MDD message timeout;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:46:36 Notice (6) CM-STATUS message sent. Event Type Code: 21; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:44:49 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:44:48 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:44:43 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:44:43 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:44:30 Warning (5) MDD message timeout;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:42:47 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:42:41 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:42:33 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:42:30 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:42:19 Warning (5) MDD message timeout;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:40:38 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:40:32 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 .;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:40:21 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
2018-05-01, 07:40:12 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:99:ce:21;CMTS-MAC=00:01:5c:84:52:6c;CM-QOS=1.1;CM-VER=3.1;
 

 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 31 819000000 Hz -7.8 dBmV 39.2 dB 1852387282 34 0
2 Locked QAM256 1 633000000 Hz -6.6 dBmV 41.1 dB 1851148511 0 0
3 Locked QAM256 2 639000000 Hz -6.5 dBmV 41.1 dB 1851157783 0 0
4 Locked QAM256 3 645000000 Hz -6.2 dBmV 41.3 dB 1851166578 0 0
5 Locked QAM256 4 651000000 Hz -6.2 dBmV 41.1 dB 1851177077 1 0
6 Locked QAM256 5 657000000 Hz -6.5 dBmV 41.1 dB 1851185394 0 0
7 Locked QAM256 6 663000000 Hz -6.6 dBmV 40.7 dB 1851194967 1 0
8 Locked QAM256 7 669000000 Hz -6.7 dBmV 40.7 dB 1851204923 2 0
9 Locked QAM256 8 675000000 Hz -6.6 dBmV 40.1 dB 1851215834 0 0
10 Locked QAM256 9 681000000 Hz -6.6 dBmV 40.7 dB 1851225024 0 0
11 Locked QAM256 10 687000000 Hz -6.6 dBmV 40.7 dB 1851234394 2 0
12 Locked QAM256 11 693000000 Hz -6.7 dBmV 40.7 dB 1851244166 1 0
13 Locked QAM256 12 699000000 Hz -6.7 dBmV 40.5 dB 1851253557 10 25
14 Locked QAM256 13 705000000 Hz -6.6 dBmV 40.5 dB 1851262312 76 0
15 Locked QAM256 14 717000000 Hz -6.5 dBmV 40.6 dB 1851272098 3 0
16 Locked QAM256 15 723000000 Hz -6.6 dBmV 40.6 dB 1851281597 1 0
17 Locked QAM256 16 729000000 Hz -6.7 dBmV 40.4 dB 1851307688 3 0
18 Locked QAM256 17 735000000 Hz -6.7 dBmV 40.2 dB 1851316549 3 0
19 Locked QAM256 18 741000000 Hz -6.8 dBmV 40.4 dB 1851326216 5 0
20 Locked QAM256 19 747000000 Hz -6.8 dBmV 40.1 dB 1851335583 7 0
21 Locked QAM256 20 753000000 Hz -6.8 dBmV 39.8 dB 1851345264 3 0
22 Locked QAM256 21 759000000 Hz -7.2 dBmV 40.0 dB 1851353997 10 0
23 Locked QAM256 22 765000000 Hz -7.3 dBmV 39.8 dB 1851363647 13 0
24 Locked QAM256 23 771000000 Hz -7.3 dBmV 39.8 dB 1851373554 15 0
25 Locked QAM256 24 777000000 Hz -7.3 dBmV 40.0 dB 1851383186 6 0
26 Locked QAM256 25 783000000 Hz -7.6 dBmV 39.7 dB 1851392409 14 0
27 Locked QAM256 26 789000000 Hz -7.6 dBmV 39.7 dB 1851401730 17 0
28 Locked QAM256 27 795000000 Hz -7.7 dBmV 39.5 dB 1851410392 22 0
29 Locked QAM256 28 801000000 Hz -7.7 dBmV 39.5 dB 1851420906 22 0
30 Locked QAM256 29 807000000 Hz -7.7 dBmV 39.4 dB 1851428571 20 0
31 Locked QAM256 30 813000000 Hz -7.6 dBmV 39.3 dB 1851433537 16 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

<tabindex=-1>Upstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 9 19300000 Hz 45.3 dBmV
2 Locked ATDMA 10 25700000 Hz 45.8 dBmV
3 Locked ATDMA 11 32300000 Hz 46.3 dBmV
4 Locked ATDMA 12 38700000 Hz 46.3 dBmV
5 Not Locked Unknown 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Hz 0.0 dBmV

<tabindex=-1>Downstream OFDM Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked 0 33 903000000 Hz -7.6 dBmV 37.3 dB 1108 ~ 2987 30876 1565 0
2 Not Locked 0 0 0 Hz -5.5 dBmV 0.0 dB 0 ~ 4095 0 0 0

<tabindex=-1>Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked Unknown 0 0 Hz 0 dBmV
2 Not Locked Unknown 0 0 Hz 0 dBmV
Expert

Re: Intermittent connection drops

I've asked an employee to check the CMTS for real-time and historical RF signal reports from your modem. They can also check your local node/plant for any degradation or error reports. You can expect a reply in this thread. 

 

If you would like to do some troubleshooting on your own:

See the troubleshooting guide.


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!