Regular Visitor
•
4 Messages
Netgear CM1200 Modem - Started Unicast Maintenance Ranging - No Response received - T3 time-out
Hello,
I am receiving a number of Critical errors on my Netgear CM1200 modem. I was hoping that someone on these forums could assist me.
I have attempted rebooting the modem and checking connections numerous times to no avail.
Here are the error messages from today. Any guidance or introduction to a Comcast employee that can assist would be greatly appreciated.
Time | Priority | Description |
Tue Jan 26 19:55:48 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:55:37 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:55:00 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:54 2021 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:53 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:51 2021 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:51 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:50 2021 | Warning (5) | Dynamic Range Window violation |
Tue Jan 26 19:54:50 2021 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:50 2021 | Warning (5) | Dynamic Range Window violation |
Tue Jan 26 19:54:50 2021 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:44 2021 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:44 2021 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:54:39 2021 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 19:50:06 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 13:02:15 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 14 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 13:02:05 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 14 28 29 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 13:01:59 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 14 29 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 13:01:58 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 13:01:56 2021 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 13:01:51 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 12:58:47 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 11:33:56 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 14; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 11:33:51 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 14 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 11:33:43 2021 | Warning (5) | MDD message timeout;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 11:33:39 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 14; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:32:10 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:09:12 2021 | Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:09:09 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:06:28 2021 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:06:27 2021 | Critical (3) | REG RSP not received;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:06:24 2021 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:06:18 2021 | Warning (5) | ToD request sent - No Response received;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:06:07 2021 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Tue Jan 26 08:06:04 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:05:54 2021 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:01:5c:74:a8:7d;CM-QOS=1.1;CM-VER=3.1; |
Tue Jan 26 08:05:48 2021 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:41:3c:b8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
103.5K Messages
3 years ago
Are you actually experiencing any connectivity problems or are you just focusing on those error log entries ?
Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
0
Geronimo926
Regular Visitor
•
4 Messages
3 years ago
Hello @EG ,
Thank you for your quick response! Here are the answers to your questions.
1. Are you actually experiencing any connectivity problems or are you just focusing on those error log entries?
Yes, our service degrades to the point of being unusable. I reboot and it seems to work again for some time and then we run into the same service issues.
2. Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
Procedure
Status
Comment
Acquire Downstream Channel
507000000 Hz
Locked
Connectivity State
OK
Operational
Boot State
OK
Operational
Security
Enabled
BPI+
IP Provisioning Mode
Honor MDD
honorMdd(4)
Channel
Lock Status
Modulation
Channel ID
Frequency
Power
SNR
Correctables
Uncorrectables
1
Locked
QAM256
20
507000000 Hz
-4.5 dBmV
38.6 dB
315
0
2
Locked
QAM256
17
483000000 Hz
-4.7 dBmV
36.7 dB
4
0
3
Locked
QAM256
18
489000000 Hz
-4.7 dBmV
34.8 dB
1
0
4
Locked
QAM256
19
495000000 Hz
-4.5 dBmV
41.4 dB
2
0
5
Locked
QAM256
21
513000000 Hz
-4.4 dBmV
40.5 dB
3
0
6
Locked
QAM256
22
519000000 Hz
-4.4 dBmV
41.6 dB
1
0
7
Locked
QAM256
23
525000000 Hz
-4.7 dBmV
41.7 dB
1
0
8
Locked
QAM256
24
531000000 Hz
-4.8 dBmV
41.7 dB
1
0
9
Locked
QAM256
25
537000000 Hz
-4.8 dBmV
41.6 dB
0
0
10
Locked
QAM256
26
543000000 Hz
-4.9 dBmV
41.6 dB
0
0
11
Locked
QAM256
27
549000000 Hz
-5 dBmV
29 dB
35718
0
12
Locked
QAM256
28
555000000 Hz
-5 dBmV
28.4 dB
1071541
1583
13
Locked
QAM256
29
561000000 Hz
-4.8 dBmV
33 dB
2635
0
14
Locked
QAM256
30
567000000 Hz
-5.1 dBmV
34.6 dB
14
0
15
Locked
QAM256
31
573000000 Hz
-5.3 dBmV
31.3 dB
1732233
3630
16
Locked
QAM256
32
579000000 Hz
-5.2 dBmV
32.4 dB
18525
0
17
Locked
QAM256
33
585000000 Hz
-5 dBmV
35.9 dB
7
0
18
Locked
QAM256
34
591000000 Hz
-5.3 dBmV
36.4 dB
29
0
19
Locked
QAM256
35
597000000 Hz
-5.4 dBmV
39.6 dB
17
0
20
Locked
QAM256
36
603000000 Hz
-5.4 dBmV
40.9 dB
8
0
21
Locked
QAM256
37
609000000 Hz
-5.7 dBmV
40.9 dB
36
0
22
Locked
QAM256
38
615000000 Hz
-6.1 dBmV
41.3 dB
20
0
23
Locked
QAM256
39
621000000 Hz
-6 dBmV
41.4 dB
17
0
24
Locked
QAM256
40
627000000 Hz
-6 dBmV
41.3 dB
109
0
25
Locked
QAM256
41
633000000 Hz
-6.3 dBmV
41.1 dB
4393
0
26
Locked
QAM256
42
639000000 Hz
-6.5 dBmV
41.1 dB
13
0
27
Locked
QAM256
43
645000000 Hz
-6.2 dBmV
41.2 dB
20
0
28
Locked
QAM256
44
651000000 Hz
-6.4 dBmV
41.1 dB
47
0
29
Locked
QAM256
45
657000000 Hz
-6.5 dBmV
41.1 dB
19
0
30
Locked
QAM256
46
663000000 Hz
-6.5 dBmV
41 dB
20
0
31
Locked
QAM256
47
669000000 Hz
-6.5 dBmV
41 dB
0
0
32
Not Locked
Unknown
0
0 Hz
0.0 dBmV
0.0 dB
0
0
Channel
Lock Status
US Channel Type
Channel ID
Symbol Rate
Frequency
Power
1
Locked
ATDMA
5
5120 Ksym/sec
17300000 Hz
51.8 dBmV
2
Locked
ATDMA
6
5120 Ksym/sec
23700000 Hz
51.5 dBmV
3
Locked
ATDMA
7
5120 Ksym/sec
30300000 Hz
51.3 dBmV
4
Locked
ATDMA
8
5120 Ksym/sec
36700000 Hz
51.3 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
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
688000000 Hz
-6.7 dBmV
40.4 dB
1108 ~ 2987
296745404
262621859
0
2
Not Locked
0
0
0 Hz
0 dBmV
0.0 dB
0 ~ 4095
0
0
0
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
Please let me know if there are any other details you need.
Many thanks, in advance, for your help and guidance.
Best,
Paul
0
0
EG
Expert
•
103.5K Messages
3 years ago
The upstream power too high and it may be intermittently fluctuating even higher to out of spec levels. And the downstream power is weak. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there 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 types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test
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.
0
Geronimo926
Regular Visitor
•
4 Messages
3 years ago
Hello @EG ,
Well that was probably the best and most detailed response I have ever had any issue I have posted on a forum! I will get to work on this and will report back if this fixes my issue(s).
Many, many thanks for taking the time to provide me with this information and solution.
Cheers,
Paul
0
0
EG
Expert
•
103.5K Messages
3 years ago
0
0
EG
Expert
•
103.5K Messages
3 years ago
For curiosity. Please post what the stats look like now.
0
0
Geronimo926
Regular Visitor
•
4 Messages
3 years ago
Hi @EG ,
I removed two unnecessary old splitters and connected the line drop directly to the cable line that goes to the modem with a VCE F-Type Coaxial RG6 3GHz Connector and things appear to be working well again.
I will double check my Event Log tomorrow and see if there are any other issues.
Thank you again for your guidance!
All the best,
Paul
0
0