U

Visitor

 • 

2 Messages

Monday, July 7th, 2025 4:13 PM

CM3000 issues? (Received Response to Broadcast Maintenance Request, But no Unicast Maintenance)

Time Priority Description
Mon Jul 07 07:58:34 2025 (Warning (5)) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:42:03 2025 (Notice (6)) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:42:02 2025 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:42:01 2025 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:41:52 2025 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Mon Jul 07 04:41:39 2025 (Warning (5)) ToD request sent - No Response received;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:41:11 2025 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:40:42 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:40:20 2025 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:40:10 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Jul 07 04:40:05 2025 (Warning (5)) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:03:51 2025 (Warning (5)) Dynamic Range Window violation
Sun Jul 06 21:03:51 2025 (Warning (5)) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:03:51 2025 (Warning (5)) Dynamic Range Window violation
Sun Jul 06 21:03:51 2025 (Warning (5)) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:03:51 2025 (Notice (6)) US profile assignment change. US Chan ID: 41; Previous Profile: 13; New Profile: 12 13.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:03:46 2025 (Notice (6)) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:03:45 2025 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:03:44 2025 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:03:34 2025 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Sun Jul 06 21:02:47 2025 (Warning (5)) ToD request sent - No Response received;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:02:43 2025 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:02:43 2025 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:02:38 2025 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:02:15 2025 (Warning (5)) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:02:11 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 21:01:39 2025 (Warning (5)) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:22:27 2025 (Notice (6)) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:22:26 2025 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:22:25 2025 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:22:16 2025 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Sun Jul 06 13:21:28 2025 (Warning (5)) ToD request sent - No Response received;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:21:23 2025 (Warning (5)) Dynamic Range Window violation
Sun Jul 06 13:21:23 2025 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:21:22 2025 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:21:17 2025 (Warning (5)) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:20:17 2025 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:20:17 2025 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Jul 06 13:20:17 2025 (Warning (5)) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat Jul 05 07:06:25 2025 (Notice (6)) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 28 543000000 Hz 4.9 dBmV 44.5 dB 1 0
2 Locked QAM256 13 453000000 Hz 4.9 dBmV 44.3 dB 2 0
3 Locked QAM256 14 459000000 Hz 5.0 dBmV 44.3 dB 5 0
4 Locked QAM256 15 465000000 Hz 5.0 dBmV 44.4 dB 7 0
5 Locked QAM256 16 471000000 Hz 5.1 dBmV 44.4 dB 1 0
6 Locked QAM256 17 477000000 Hz 5.0 dBmV 44.3 dB 1 0
7 Locked QAM256 18 483000000 Hz 5.0 dBmV 44.4 dB 0 0
8 Locked QAM256 19 489000000 Hz 5.1 dBmV 44.5 dB 2 0
9 Locked QAM256 20 495000000 Hz 5.1 dBmV 44.5 dB 2 0
10 Locked QAM256 21 501000000 Hz 5.1 dBmV 44.5 dB 2 0
11 Locked QAM256 22 507000000 Hz 5.0 dBmV 44.5 dB 3 0
12 Locked QAM256 23 513000000 Hz 5.1 dBmV 44.6 dB 7 0
13 Locked QAM256 24 519000000 Hz 5.1 dBmV 44.6 dB 6 0
14 Locked QAM256 25 525000000 Hz 5.0 dBmV 44.5 dB 1 0
15 Locked QAM256 26 531000000 Hz 4.8 dBmV 44.4 dB 1 0
16 Locked QAM256 27 537000000 Hz 4.9 dBmV 44.6 dB 2 0
17 Locked QAM256 29 549000000 Hz 4.9 dBmV 44.6 dB 5 0
18 Locked QAM256 30 555000000 Hz 4.9 dBmV 44.5 dB 1 0
19 Locked QAM256 31 561000000 Hz 5.0 dBmV 44.7 dB 7 0
20 Locked QAM256 32 567000000 Hz 5.0 dBmV 44.7 dB 7 0
21 Locked QAM256 33 573000000 Hz 5.0 dBmV 44.7 dB 4 0
22 Locked QAM256 34 579000000 Hz 5.1 dBmV 44.8 dB 1 0
23 Locked QAM256 35 585000000 Hz 5.1 dBmV 44.8 dB 1 0
24 Locked QAM256 36 591000000 Hz 5.2 dBmV 44.9 dB 1 0
25 Locked QAM256 37 597000000 Hz 5.2 dBmV 45.0 dB 5 0
26 Locked QAM256 38 603000000 Hz 5.2 dBmV 45.0 dB 2 0
27 Locked QAM256 39 609000000 Hz 5.3 dBmV 45.0 dB 2 0
28 Locked QAM256 40 615000000 Hz 5.3 dBmV 45.0 dB 2 0
29 Locked QAM256 41 621000000 Hz 5.3 dBmV 45.1 dB 7 0
30 Locked QAM256 42 627000000 Hz 5.3 dBmV 45.1 dB 2 0
31 Locked QAM256 43 633000000 Hz 5.4 dBmV 45.1 dB 5 0
32 Locked QAM256 44 639000000 Hz 5.3 dBmV 44.7 dB 2 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 37.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 37.0 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 37.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 38.0 dBmV
5 Not Locked Unknown 0 0 0 0.0 dBmV
6 Not Locked Unknown 0 0 0 0.0 dBmV
7 Not Locked Unknown 0 0 0 0.0 dBmV
8 Not Locked Unknown 0 0 0 0.0 dBmV
 
Downstream OFDM Channels
Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1 Locked 0 ,1 ,2 ,3 193 722000000 Hz 6.28 dBmV 45.2 dB 388 ~ 3707 1803971923 273851044 0
2 Locked 0 ,1 ,2 ,3 194 957000000 Hz 6.88 dBmV 44.5 dB 148 ~ 3947 1820425426 94258338 0
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Locked 12 ,13 41 36200000 Hz 32.5 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV

I have upgraded my Xfinity service to the highest they offer in my area so I have 2100/300~ give or take back in April. I bought a CM3000 from NetGear and for the past few months things were working great. I feel like in the last 4 weeks though, things have gone downhill dramatically. Usually once a day service drops completely for a few moments. It isn't xfinity as no outages are ever reported. Twice in the last month I've had to power cycle the modem completely for it to reconnect. I've started a charge-back with my credit card and a support for a refund with NetGear directly, but it occurred to me now that I might find another answer in these logs. Is there anything here that makes sense to anyone for me to try? I would hate to get a new modem from netgear or another company only to find similar issues-- leading to the real root of the problem not being modem related!

Expert

 • 

111.5K Messages

10 hours ago

The signal status values at that snapshot in time were OK but the error log entries indicate 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 values 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 (The Digital Care Team) who 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 those upstream receive signal stats.


You should get a reply here in your topic. Good luck !

Official Employee

 • 

316 Messages

10 hours ago

Good afternoon user_0a48rc. I can certainly understand the concern if you are experiencing service issues. What troubleshooting steps have you taken so far? We can look into this with you further. 

 

Visitor

 • 

2 Messages

Hi, honestly I am kinda surprised I am having any issues at all since the issues didn't originally occur when I signed up for a newer, faster, service plan. It took a few months before I started getting service drop issues. My unifi setup was logging it all and showed that it was experiencing high ping then service outage than service resumed. This would happen at least once a day, sometimes more, for a few minutes. The only thing I've done was twice fully cycle the modem because it locked up and wouldn't restore service. After 10 minutes of being fully unplugged I would reconnect everything and service would resume. My speeds have been fine for the most part. When the tech came during the initial setup visit he did add a filter or something outside the house. Aside from that nothing else has changed. 

Official Employee

 • 

316 Messages

I would be happy to assist with some troubleshooting from this end for the intermittent internet issues. I would need some additional information from you.

Please send us a direct chat message with your full name and complete service address to “Xfinity Support”. To do so, click on the chat icon located at the top right of this forums page.

 

To send a "Direct Message" to Xfinity Support:

 

Click "Sign In" if necessary

Click the "Direct Messaging" icon or  https://forums.xfinity.com/direct-messaging

Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there

As you are typing a drop-down list appears. Select "Xfinity Support" from that list

An "Xfinity Support" graphic replaces the "To:" line

Type your message in the text area near the bottom of the window and press Enter to send it.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Expert

 • 

111.5K Messages

10 hours ago

@XfinityJon 

Please poll for those upstream items as I stated above and requested in the escalation. Thank you.

forum icon

New to the Community?

Start Here