NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
merrywhether
Aug 30, 2023Aspirant
CM1000 intermittent outages from T4 resets
I've been troubleshooting intermittent connection outages for a while and first spent a lot of time on my router because it had the cursed ASUS firmware over the summer and I no longer trusted it. Finally ruling that out and replacing all ethernet cables, I moved onto my modem and the logs seem to reveal a common source of this issue: T4 timeouts. Concurrent with the latest outage I saw:
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<removed>;CMTS-MAC=00:aa:6e:c0:af:8f;CM-QOS=1.1;CM-VER=3.1;
I also saw a T3 timeout earlier but there was no corresponding outage:
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<removed>;CMTS-MAC=00:aa:6e:c0:af:8f;CM-QOS=1.1;CM-VER=3.1;
These outages occur for all devices on my network, both wired and wireless. The router's traffic monitor shows upload and download speed crater to <1kbps (which I'm assuming is actually zero). They occur daily but at random times making testing fairly difficult.
I had a technician scheduled for tomorrow but I've delayed them two days to troubleshoot a bit more from this info. This sounds similar to other issues like https://community.netgear.com/t5/Cable-Modems-Gateways/c7000v2-resets/td-p/2028769 so I'm hoping that my connection info can point me in the right direction. So far:
- I've had the ISP (Cox) send various forms of reset signals to the modem but have not yet done a factory reset (not sure if that is functionally different).
- I've ordered a new coax cable to test the path to the wall tomorrow (though like the other cables I have no reason to doubt this one other than being thorough).
- I live in an apartment building so I'm not 100% sure about the wiring, but I believe I'm connected to the jack closest to the source. After looking in building's utility closet I definitely have some questions about the cables in there (picture attached below).
Am I on the right track? Do the power and error values indicate anything in particular? Anything else I should be doing or not doing? And what should I tell the tech if/when they arrive? What are the odds the modem itself has gone bad in ~2 years?
| 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. | |
|
Startup Procedure
| Procedure | Status | Comment |
| Acquire Downstream Channel | 237000000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Security | Enable | BPI+ |
| IP Provisioning Mode | Honor MDD | IPv4 only |
Downstream Bonded Channels (Partial Service)
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR / MER | Unerrored Codewords | Correctable Codewords | Uncorrectable Codewords |
| 1 | Locked | QAM256 | 45 | 237000000 Hz | -7.7 dBmV | 42.4 dB | 839104368 | 76801 | 178537 |
| 2 | Locked | QAM256 | 1 | 735000000 Hz | -4.7 dBmV | 43.3 dB | 837770830 | 101 | 2 |
| 3 | Locked | QAM256 | 2 | 741000000 Hz | -4.6 dBmV | 43.5 dB | 837773770 | 102 | 0 |
| 4 | Locked | QAM256 | 3 | 747000000 Hz | -4.6 dBmV | 43.5 dB | 837777723 | 96 | 0 |
| 5 | Locked | QAM256 | 4 | 753000000 Hz | -4.6 dBmV | 43.6 dB | 837782395 | 62 | 0 |
| 6 | Locked | QAM256 | 5 | 759000000 Hz | -4.7 dBmV | 43.4 dB | 837787078 | 84 | 0 |
| 7 | Locked | QAM256 | 6 | 765000000 Hz | -4.9 dBmV | 43.3 dB | 837791283 | 98 | 4 |
| 8 | Locked | QAM256 | 7 | 771000000 Hz | -4.9 dBmV | 43.4 dB | 837795074 | 95 | 2 |
| 9 | Locked | QAM256 | 8 | 777000000 Hz | -5.1 dBmV | 43.2 dB | 837798652 | 84 | 2 |
| 10 | Locked | QAM256 | 25 | 117000000 Hz | -7.7 dBmV | 41.6 dB | 485251150 | 143833 | 325996 |
| 11 | Locked | QAM256 | 26 | 123000000 Hz | -7.6 dBmV | 41.8 dB | 690033220 | 163975 | 390868 |
| 12 | Locked | QAM256 | 27 | 129000000 Hz | -7.6 dBmV | 42.0 dB | 621800109 | 262519 | 363908 |
| 13 | Locked | QAM256 | 28 | 135000000 Hz | -7.7 dBmV | 42.1 dB | 766127526 | 437302 | 593842 |
| 14 | Locked | QAM256 | 29 | 141000000 Hz | -7.9 dBmV | 42.1 dB | 766052900 | 413231 | 629905 |
| 15 | Locked | QAM256 | 30 | 147000000 Hz | -7.8 dBmV | 42.1 dB | 774762502 | 407304 | 665968 |
| 16 | Locked | QAM256 | 31 | 153000000 Hz | -7.9 dBmV | 42.3 dB | 766456684 | 319473 | 588048 |
| 17 | Locked | QAM256 | 32 | 159000000 Hz | -7.8 dBmV | 42.6 dB | 692655942 | 238875 | 463220 |
| 18 | Locked | QAM256 | 33 | 165000000 Hz | -7.6 dBmV | 42.7 dB | 629332735 | 206123 | 415809 |
| 19 | Locked | QAM256 | 34 | 171000000 Hz | -7.4 dBmV | 42.8 dB | 766607358 | 147331 | 324084 |
| 20 | Locked | QAM256 | 35 | 177000000 Hz | -7.1 dBmV | 42.9 dB | 837322068 | 159840 | 348792 |
| 21 | Locked | QAM256 | 36 | 183000000 Hz | -7.1 dBmV | 42.9 dB | 746984837 | 109809 | 271674 |
| 22 | Locked | QAM256 | 37 | 189000000 Hz | -7.2 dBmV | 42.9 dB | 629089739 | 88838 | 230675 |
| 23 | Locked | QAM256 | 38 | 195000000 Hz | -7.1 dBmV | 43.0 dB | 644609688 | 84716 | 234953 |
| 24 | Locked | QAM256 | 39 | 201000000 Hz | -7.1 dBmV | 43.1 dB | 810574476 | 96449 | 254230 |
| 25 | Locked | QAM256 | 40 | 207000000 Hz | -7.2 dBmV | 42.9 dB | 546789089 | 57402 | 171298 |
| 26 | Locked | QAM256 | 41 | 213000000 Hz | -7.1 dBmV | 42.9 dB | 760158593 | 74389 | 208946 |
| 27 | Locked | QAM256 | 42 | 219000000 Hz | -7.4 dBmV | 42.8 dB | 630688996 | 63471 | 170200 |
| 28 | Locked | QAM256 | 43 | 225000000 Hz | -7.6 dBmV | 42.6 dB | 837571437 | 83680 | 208837 |
| 29 | Locked | QAM256 | 44 | 231000000 Hz | -7.9 dBmV | 42.5 dB | 837597072 | 78515 | 192616 |
| 30 | Locked | QAM256 | 46 | 243000000 Hz | -7.9 dBmV | 42.5 dB | 837622196 | 85286 | 161454 |
| 31 | Locked | QAM256 | 47 | 249000000 Hz | -8.1 dBmV | 42.3 dB | 837731971 | 78357 | 58272 |
| 32 | Locked | QAM256 | 48 | 255000000 Hz | -7.8 dBmV | 42.3 dB | 837865439 | 2638 | 777 |
Upstream Bonded Channels
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power |
| 1 | Locked | ATDMA | 1 | 17600000 Hz | 54.5 dBmV |
| 2 | Locked | ATDMA | 2 | 24000000 Hz | 54.0 dBmV |
| 3 | Locked | ATDMA | 3 | 30400000 Hz | 53.5 dBmV |
| 4 | Locked | ATDMA | 4 | 36800000 Hz | 54.3 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, 1, 2, 3 | 159 | 300000000 Hz | -6.2 dBmV | 39.3 dB | 296 ~ 7895 | 285958816 | 138243565 | 540 |
| 2 | Locked | 0, 1, 2, 3 | 160 | 918000000 Hz | -4.9 dBmV | 41.5 dB | 1108 ~ 2987 | 219933960 | 100992670 | 2 |
Upstream OFDMA Channels
| Channel | Lock Status | Modulation / Profile ID | Channel ID | Frequency | Power |
| 1 | Locked | 3, 4, 9, 10, 11, 12, 13 | 6 | 36800000 Hz | 48.5 dBmV |
| 2 | Not Locked | 3, 4, 9, 10, 11, 12, 13 | 0 | 0 Hz | 0.0 dBmV |
Power is too low and out of spec:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
Lots of Corrrectables and UN-correctables that should be mostly zeros.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/
3 Replies
- merrywhetherAspirant
Looking at the Netgear firmware chart, I noticed that supposedly the latest general firmware for the CM1000 is V7.01.01 while Cox is supposedly on V3.01.04, and I'm sitting in the middle somehow at V6.01.07. I'm guessing that perhaps Cox has done some updates since the chart was last updated in April 2023.
- FURRYe38Guru - Experienced User
Power is too low and out of spec:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
Lots of Corrrectables and UN-correctables that should be mostly zeros.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/- merrywhetherAspirant
This was super helpful, thanks! The tech wound up noticing some transient packet loss that he wouldn't have dug for had I not had this info. ISP wound upping the power at the utility pole and my power level are now middle of range and things have been much better.