NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM 1000 T3 and T4 connection timeouts persistent for years now?
There are a number of similar posts and messages in this support forum regarding the same connection issues with the Netgear CM1000 DOCSIS 3.1 cable modem. It seems that the issues persist even years after the initial problems were detected and, allegedly, resolved through firmware updates. According to the support --> firmware/software page, I have the latest firmware version installed by my ISP (RCN). However, the same connection issues are seen in the event logs as the other related forum threads here. The problems were not there while I was leasing a modem from the ISP.
Time Priority Description 2019-07-11, 06:12:30 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:25 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 .;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-11, 06:12:16 Error (4) Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 23:02:13 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;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:a5:83:48;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:13:55 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:13:45 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:13:35 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:13:15 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:08:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:08:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:06:57 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:06:56 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:06:39 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:06:26 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:05:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:05:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:05:40 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:05:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:05:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:05:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:03:17 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:02:47 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1; 2019-07-10, 21:02:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:a5:83:48;CMTS-MAC=00:af:1f:1e:b4:ea;CM-QOS=1.1;CM-VER=3.1;
4 Replies
Something to have your ISP review with you to see if there is any issues.
Be sure ISP checks signal line quality and levels up to the modem.
Be sure there are no coax cable line splitters inbetween the modem and ISP service box.
I only have Internet service; i.e. single coax line. I did call to make sure the modem was provisioned correctly after I kept noticing service interruptions. Aside from the modem itself, I don't see anything else that's changed.
Additionally, I've also noticed the logs show warnings about dynamic range window violations.
The pertinent downstream/upstream info:
Upstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 4 36800000 Hz 27.5 dBmV 2 Locked ATDMA 5 30350000 Hz 27.0 dBmV 3 Locked ATDMA 6 23900000 Hz 26.5 dBmV 4 Not Locked Unknown 0 0 Hz 0.0 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 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, 255 159 651000000 Hz 18.4 dBmV 33.3 dB 646 ~ 3449 1906011210 1481183335 824 2 Not Locked 0, 255 0 0 Hz 3.4 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 Unknown 0 0 Hz 0 dBmV 2 Not Locked Unknown 0 0 Hz 0 dBmV
Something to ask the ISP about...
