X

Visitor

 • 

3 Messages

Sun, Aug 7, 2022 1:56 AM

Regular disconnects - MDD timeout and T3 / T4 timeout

Hi,

For the past week, I've been getting regular disconnects on a daily basis at about the same time. The connection is stable and working fine all day, then at 6pm - 7pm I start getting disconnects. Sometimes just one, sometimes repeated over a period of one hour or so.

I've pasted the connection parameters and Log readout below.

Any idea what could be causing this? I've called Xfinity support but didn't get to a resolution.

Any help appreciated, thanks!

Christine

Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

<tabindex=-1>Startup Procedure</tabindex=-1>
Procedure Status Comment
Acquire Downstream Channel 405000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 4 405000000 Hz 2.2 dBmV 40.8 dB 2140784229 992464 4018396
2 Locked QAM256 5 411000000 Hz 2.1 dBmV 40.8 dB 2139574616 994176 4031996
3 Locked QAM256 6 417000000 Hz 2.1 dBmV 40.8 dB 2139544834 993835 4026834
4 Locked QAM256 7 423000000 Hz 2.4 dBmV 41.4 dB 2139571681 995551 4039514
5 Locked QAM256 8 429000000 Hz 2.5 dBmV 41.1 dB 2139560002 993592 4034990
6 Locked QAM256 9 435000000 Hz 2.3 dBmV 40.9 dB 2139567422 999548 4047745
7 Locked QAM256 10 441000000 Hz 2.0 dBmV 40.5 dB 2139567749 1000646 4052994
8 Locked QAM256 11 447000000 Hz 1.7 dBmV 40.6 dB 2139556212 1002525 4052359
9 Locked QAM256 12 453000000 Hz 1.9 dBmV 40.7 dB 2139586209 1001193 4059515
10 Locked QAM256 13 459000000 Hz 2.2 dBmV 40.8 dB 2139592519 1000082 4054297
11 Locked QAM256 14 465000000 Hz 2.3 dBmV 40.4 dB 2139606233 997653 4048949
12 Locked QAM256 15 471000000 Hz 2.4 dBmV 41.1 dB 2139608560 998766 4048040
13 Locked QAM256 16 477000000 Hz 2.2 dBmV 40.9 dB 2139615792 1000072 4043683
14 Locked QAM256 17 483000000 Hz 1.9 dBmV 40.6 dB 2139607242 995426 4038777
15 Locked QAM256 18 489000000 Hz 1.9 dBmV 40.1 dB 2139616869 994852 4023601
16 Locked QAM256 19 495000000 Hz 1.9 dBmV 40.6 dB 2139652394 990083 4014822
17 Locked QAM256 20 507000000 Hz 2.1 dBmV 40.5 dB 2139701001 986713 3986025
18 Locked QAM256 21 513000000 Hz 1.9 dBmV 40.5 dB 2139689418 978836 3958931
19 Locked QAM256 22 519000000 Hz 1.8 dBmV 40.7 dB 2139736099 978978 3957071
20 Locked QAM256 23 525000000 Hz 1.9 dBmV 40.6 dB 2139715723 969398 3929322
21 Locked QAM256 24 531000000 Hz 2.1 dBmV 40.8 dB 2139761429 969377 3933272
22 Locked QAM256 25 537000000 Hz 2.2 dBmV 41.0 dB 2139780119 970966 3942237
23 Locked QAM256 26 543000000 Hz 1.9 dBmV 40.7 dB 2139760924 975828 3951070
24 Locked QAM256 27 549000000 Hz 1.5 dBmV 40.2 dB 2139747269 979457 3975498
25 Locked QAM256 28 555000000 Hz 1.4 dBmV 40.0 dB 2139730910 986152 3990930
26 Locked QAM256 29 561000000 Hz 1.7 dBmV 40.3 dB 2139742297 981488 3986263
27 Locked QAM256 30 567000000 Hz 2.1 dBmV 40.8 dB 2139757272 978764 3978397
28 Locked QAM256 31 573000000 Hz 2.4 dBmV 40.7 dB 2139750649 980826 3985654
29 Locked QAM256 32 579000000 Hz 2.2 dBmV 40.6 dB 2139735860 983839 4002581
30 Locked QAM256 33 585000000 Hz 1.9 dBmV 40.3 dB 2139701368 990565 4031338
31 Locked QAM256 34 591000000 Hz 1.8 dBmV 40.2 dB 2139657763 999027 4065981
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 1 10400000 Hz 44.5 dBmV
2 Locked ATDMA 2 16400000 Hz 44.3 dBmV
3 Locked ATDMA 3 22800000 Hz 44.8 dBmV
4 Locked ATDMA 4 29200000 Hz 46.0 dBmV
5 Locked ATDMA 5 35600000 Hz 45.0 dBmV
6 Locked ATDMA 6 40400000 Hz 45.5 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</tabindex=-1>
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, 1, 2, 3 48 850000000 Hz 0.9 dBmV 35.8 dB 1108 ~ 2987 3557664046 3223847532 17461428
2 Not Locked 0 0 0 Hz 3.9 dBmV 0.0 dB 0 ~ 4095 0 0 0

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
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

Current System Time: Sat Aug 06 17:48:24 2022
System Up Time: 65:38:11

Time Priority Description
2022-08-06, 17:47:09 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:46:47 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:45:59 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:44:39 Notice (6) CM-STATUS message sent. Event Type Code: 6; Chan ID: 1; 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;
2022-08-06, 17:44:39 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;
2022-08-06, 17:42:52 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:42:44 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;
2022-08-06, 17:42:42 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:42:35 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;
2022-08-06, 17:42:32 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:42:20 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;
2022-08-06, 17:42:14 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:41:58 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:41:48 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:40:44 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:40:22 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:37:42 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;
2022-08-06, 17:36:44 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:36:37 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;
2022-08-06, 17:35:57 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:35:56 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;
2022-08-06, 17:35:53 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 6 17; 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;
2022-08-06, 17:35:52 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:35:50 Warning (5) MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:35:47 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:35:46 Warning (5) Dynamic Range Window violation
2022-08-06, 17:35:46 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;
2022-08-06, 17:35:45 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;
2022-08-06, 17:29:00 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:28:33 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:27:56 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:27:40 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:27:31 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:27:10 Warning (5) Dynamic Range Window violation
2022-08-06, 17:27:10 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;
2022-08-06, 17:26:53 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:26:44 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:26:15 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:26:12 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
2022-08-06, 17:24:58 Notice (6) CM-STATUS message sent. Event Type Code: 6; Chan ID: 1; 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;
EG

Expert

 • 

95.8K Messages

2 m مضت

Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".

Official Employee

 • 

191 Messages

2 m مضت

Hello @xarnould We appreciate you taking the time to reach out to us today. I know how frustrating it is when the Internet isn't working and we'd be happy to help troubleshoot. 

 

Could you please send our team a direct message with your full name and full address? Our team can most definitely take a further look at this issue.
To send a "Peer to peer" ("Private") message:
Click "Sign In" if necessary
• Click the "Peer to peer chat" icon
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "Xfinity Support" graphic replaces the "To:" line
• Type your message in the text area near the bottom of the window
• Press Enter to send it

Visitor

 • 

3 Messages

@XfinityJessicaA​ 

Hi Jessica,

Thanks for your response. I sent a messate to Xfinity support a few days ago, but never received a response. Is anybody monitoring that account and responding?

Best,

Christine

Official Employee

 • 

124 Messages

@xarnould Thank you for reaching back out to us here at the Xfinity Community Forums. When you create a public post requesting assistance, we do request that you wait for a Comcast verified employee to respond and ask for a private message to be sent before you proceed with doing so. Please note that sending unsolicited direct messages to an Official Employee of the Xfinity Help & Support Forums is a violation of our Forum Guidelines It looks like your prior DM was sent before being requested in our public response, so this is likely the reason why.

I would be more than happy to continue assisting you with your connection concern via DM this time, however!

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
forum icon

New to the Community?

Start Here