user_nvc75f's profile

Sunday, March 31st, 2024 5:03 PM

Occasional conncetion issues with Netgear CM1200 (Errors: Unicast Maintenance Ranging, T3 timeout, MDD message timeout)

Hello,

I get inconsistent performance and connectivity with my service.  My cable connection numbers seem clean, but I am getting many errors in the logs on my cable modem. 

Any advice?  Please see the data listed below.

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
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 531000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 531000000 Hz 4.7 dBmV 45.2 dB 0 0
2 Locked QAM256 13 489000000 Hz 5.1 dBmV 45.6 dB 0 0
3 Locked QAM256 14 495000000 Hz 5.2 dBmV 45.6 dB 0 0
4 Locked QAM256 15 501000000 Hz 5.2 dBmV 44.9 dB 0 0
5 Locked QAM256 16 507000000 Hz 5.1 dBmV 45 dB 0 0
6 Locked QAM256 17 513000000 Hz 5 dBmV 45.4 dB 0 0
7 Locked QAM256 18 519000000 Hz 4.9 dBmV 45.3 dB 0 0
8 Locked QAM256 19 525000000 Hz 4.9 dBmV 45.2 dB 0 0
9 Locked QAM256 21 537000000 Hz 4.6 dBmV 45.1 dB 0 0
10 Locked QAM256 22 543000000 Hz 4.5 dBmV 45.1 dB 0 0
11 Locked QAM256 23 549000000 Hz 4.4 dBmV 45 dB 0 0
12 Locked QAM256 24 555000000 Hz 4.6 dBmV 45 dB 0 0
13 Locked QAM256 25 561000000 Hz 4.9 dBmV 45 dB 0 0
14 Locked QAM256 26 567000000 Hz 5 dBmV 45.1 dB 0 0
15 Locked QAM256 27 573000000 Hz 5.2 dBmV 45.1 dB 0 0
16 Locked QAM256 28 579000000 Hz 5.4 dBmV 45.2 dB 0 0
17 Locked QAM256 29 585000000 Hz 5.4 dBmV 45.3 dB 0 0
18 Locked QAM256 30 591000000 Hz 5.4 dBmV 45.3 dB 0 0
19 Locked QAM256 31 597000000 Hz 5.3 dBmV 45.2 dB 0 0
20 Locked QAM256 32 603000000 Hz 5.1 dBmV 45 dB 0 0
21 Locked QAM256 33 609000000 Hz 4.8 dBmV 44.9 dB 0 0
22 Locked QAM256 34 615000000 Hz 4.7 dBmV 44.8 dB 0 0
23 Locked QAM256 35 621000000 Hz 5 dBmV 44.9 dB 0 0
24 Locked QAM256 36 627000000 Hz 5 dBmV 44.9 dB 0 0
25 Locked QAM256 37 633000000 Hz 5.1 dBmV 44.9 dB 0 0
26 Locked QAM256 38 639000000 Hz 5.1 dBmV 44.9 dB 0 0
27 Locked QAM256 39 645000000 Hz 5.3 dBmV 44.9 dB 0 0
28 Locked QAM256 40 651000000 Hz 5.6 dBmV 44.9 dB 0 0
29 Locked QAM256 41 657000000 Hz 5.7 dBmV 45 dB 0 0
30 Locked QAM256 42 663000000 Hz 5.9 dBmV 45 dB 0 0
31 Locked QAM256 43 669000000 Hz 5.9 dBmV 45 dB 0 0
32 Locked QAM256 44 675000000 Hz 5.7 dBmV 44.1 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 17 5120 Ksym/sec 16400000 Hz 48.8 dBmV
2 Locked ATDMA 18 5120 Ksym/sec 22800000 Hz 48.8 dBmV
3 Locked ATDMA 19 5120 Ksym/sec 29200000 Hz 49 dBmV
4 Locked ATDMA 20 5120 Ksym/sec 35600000 Hz 49 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
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 ,1 ,2 ,3 193 957000000 Hz 7.0 dBmV 44.3 dB 148 ~ 3947 949719107 13309008 84
2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0
 
Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Sun Mar 31 08:53:57 2024
System Up Time:21:33:35

Time Priority Description
Sun Mar 31 08:52:49 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 05:55:24 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 05:54:55 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 05:46:09 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 04:21:55 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 04:21:26 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 04:21:21 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 04:18:54 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 04:18:25 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 04:18:19 2024 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;
Sun Mar 31 00:48:01 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 00:47:50 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 00:47:31 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sun Mar 31 00:46:40 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 20:17:55 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 20:17:26 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 20:02:21 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 19:14:26 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 19:14:00 2024 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;
Sat Mar 30 19:13:53 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 18:55:18 2024 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;
Sat Mar 30 18:53:00 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 18:52:31 2024 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;
Sat Mar 30 18:52:31 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 18:52:29 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 18:52:27 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 18:48:46 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 18:13:57 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 18:13:28 2024 Warning (5) MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 17:57:26 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 17:56:57 2024 Warning (5) MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 17:56:55 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 16:13:56 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 16:13:26 2024 Warning (5) MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 16:13:25 2024 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;
Sat Mar 30 16:13:25 2024 Warning (5) MDD message timeout;CM-MAC=[Edited: Personal Information];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 16:13:25 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 14:31:25 2024 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 14:30:56 2024 Warning (5) MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 30 14:30:52 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;

Accepted Solution

Official Employee

 • 

825 Messages

20 days ago

@user_nvc75f Hello, thanks for reaching out for help on our Forums! I'm sorry to hear that you have had these hiccups in connections. I know first hand how a small interruption can cause a big headache. You are with the right team for help to troubleshoot and resolve the issues. 
@EG Thank you for assisting us. You mentioned all the things to check to help with the signal issue and even the timeouts, but if those checks and changes don't result well we can set up a repair appointment. 
@user_nvc75f Please let us know if any of these steps help out. If not we will set up a time for a repair technician to help us out. 

2 Messages

Hello,

I just had a tech out here less than two weeks ago. He ran diagnostics on the line and replaced an old cable fitting.

A single splitter is installed on the street line with the service branching out to an Xfinity DVR and the cable modem, each on a dedicated cable.  No other devices or even coax cables are connected to the network.  There is a filter installed between the connection coming from the street and the splitter.

All couplers, fittings, and wall jacks are rated to 3GHz.

Official Employee

 • 

514 Messages

 

user_nvc75f I appreciate that information, and we would need to get another technican scheduled to help get this resolved since the issue is still present. To send a direct message, please click on the chat icon in the top-right corner of the screen, and select "Xfinity Support" to initiate a Direct Message. 
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
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

 

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

 • 

103.3K Messages

22 days ago

@user_nvc75f 

Please redact all of the CM MAC and the CMTS MAC addresses from 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".

(edited)

Expert

 • 

103.3K Messages

22 days ago

@user_nvc75f 

This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless.

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

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are 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 from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

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.


Good luck with it !

forum icon

New to the Community?

Start Here