NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Cox-Me-Nitgear
Dec 10, 2021Aspirant
COX says to call Netgear - Netgear says to call COX
Hi team, Our Cox ISP FSE came to our house and determined that the connectivity problems were caused by our CM1200 modem. He recommended a firmware update. Ok great. But how do we update the f...
FURRYe38
Dec 11, 2021Guru - Experienced User
Yes, there are "Some" ISPs that don't update "user owned" modems. ISP owned yes. This varies from ISP to ISP.
The reason why users are not allowed to update FW is that this has been a DOCSIS policy standard for many years. Please, contact the DOCSIS community developers and post your concerns there. They are in charge of how cable modems operate.
One reason why it came about is that Cables ISPs early on didn't have good testing methods in place for testing new modems and FW out. I'm sure there was some non communication handling as well between modem mfrs and ISPs. Modem mfrs would just hand out FW to the ISPs and thinking that the modem mfr was doing due diligence in testing, ISP would push FW to user owned modems and either bugs caused problems or the push would brick the users modem. Thus incurring costs for the ISP to replaced the user owned modems. So due to this, ISPs are now responsible for testing any new FW that the mfr hands them prior to pushing to ANY modem. However 'some' cables ISPs took the stance of to avoid any kind of modem liability, 'some' cable ISP will NOT update user owned modems period. They will only push to ISP owned modems. Not all cable ISPs take this stance. Apparently Cox does. I know Spectrum is another that seems problematic for users owned modems.
If your modem isn't locking in on channels, there maybe a signal line or cable line problem rather a FW issue. Not everything is fixed by FW.
Please post a copy and paste of the modems connection status page.
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.
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
For ISPs that just won't update user owned modems and users seem to have problems with the modems they buy, we recommend to avoid the hassles and use the ISP owned modem, even if you have to rent it.
Cox-Me-Nitgear wrote:
[quote]ALL Cable ISPs are responcible for updateing FW ON ALL cable modems. There NO user modems that users can udpate, sans CAX series which users can update the router side of this product. The modem side still requires the cable ISP to update the modems FW. No exceptions.[/quote]
Well, here in Mesa Arizona things are different. Cox ** DOES NOT ** push updates on 3rd party modems.
We've been down the rabbit hole of questioning our router(s) and devices(s), sorry. I trust our Cox FSE who showed us exactly what was going on at the modem. Forget the router. Our Netgear CM1200 could not lock on the downstream signal while his monitoring device had no problem whatsoever. We repeated the test several times, same result.
We own this modem and I think that we should be able to push our own updates, as Cox is telling us to do. So why is Netgear not allowing users to update? [Head scratcher].
So… we went with Cox Panoramic Wifi solution. We should have the hardware in a couple days. We are keeping our CM1200 for now until we get comparative test results with the Cox device.
Cox-Me-Nitgear
Dec 11, 2021Aspirant
FURRYe38 wrote:
For ISPs that just won't update user owned modems and users seem to have problems with the modems they buy, we recommend to avoid the hassles and use the ISP owned modem, even if you have to rent it.
Thank you Furry for your post. Yes it absolutely makes sense to question the line from Cox, splitters and cabling. But according to 3 different service techs who came to our house in the past few weeks they all confirmed that the signal at the modem is good.
Here is a copy/paste of our status page... we just had an "outage" as I am typing this reply...
| 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 | 951000000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Security | Enabled | BPI+ |
| IP Provisioning Mode | Honor MDD | honorMdd(4) |
Downstream Bonded Channels (Partial Service)
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Correctables | Uncorrectables |
| 1 | Locked | QAM256 | 29 | 951000000 Hz | 2.4 dBmV | 44.1 dB | 0 | 0 |
| 2 | Locked | QAM256 | 5 | 807000000 Hz | 1 dBmV | 44.3 dB | 14 | 0 |
| 3 | Locked | QAM256 | 9 | 831000000 Hz | 1.3 dBmV | 44.1 dB | 0 | 0 |
| 4 | Locked | QAM256 | 10 | 837000000 Hz | 1.3 dBmV | 44.2 dB | 0 | 0 |
| 5 | Locked | QAM256 | 11 | 843000000 Hz | 1.5 dBmV | 44.1 dB | 0 | 0 |
| 6 | Locked | QAM256 | 12 | 849000000 Hz | 1.7 dBmV | 44.3 dB | 0 | 0 |
| 7 | Locked | QAM256 | 14 | 861000000 Hz | 1.5 dBmV | 44.1 dB | 0 | 0 |
| 8 | Locked | QAM256 | 18 | 885000000 Hz | 2 dBmV | 44.3 dB | 0 | 0 |
| 9 | Locked | QAM256 | 19 | 891000000 Hz | 1.9 dBmV | 44.2 dB | 0 | 0 |
| 10 | Locked | QAM256 | 20 | 897000000 Hz | 1.9 dBmV | 44.2 dB | 0 | 0 |
| 11 | Locked | QAM256 | 22 | 909000000 Hz | 2.3 dBmV | 44.2 dB | 0 | 0 |
| 12 | Locked | QAM256 | 23 | 915000000 Hz | 2.3 dBmV | 44.1 dB | 0 | 0 |
| 13 | Locked | QAM256 | 24 | 921000000 Hz | 2.2 dBmV | 44.1 dB | 0 | 0 |
| 14 | Locked | QAM256 | 25 | 927000000 Hz | 2 dBmV | 44 dB | 0 | 0 |
| 15 | Locked | QAM256 | 26 | 933000000 Hz | 2.2 dBmV | 44.1 dB | 0 | 0 |
| 16 | Locked | QAM256 | 27 | 939000000 Hz | 2.3 dBmV | 44.1 dB | 0 | 0 |
| 17 | Locked | QAM256 | 28 | 945000000 Hz | 2.5 dBmV | 44.2 dB | 0 | 0 |
| 18 | Locked | QAM256 | 30 | 957000000 Hz | 2.3 dBmV | 44 dB | 0 | 0 |
| 19 | Locked | QAM256 | 31 | 963000000 Hz | 2.4 dBmV | 44.2 dB | 0 | 0 |
| 20 | Locked | QAM256 | 32 | 969000000 Hz | 2.6 dBmV | 44.4 dB | 0 | 0 |
| 21 | Locked | QAM256 | 37 | 381000000 Hz | 0.1 dBmV | 45.1 dB | 0 | 0 |
| 22 | Locked | QAM256 | 38 | 387000000 Hz | 0.3 dBmV | 45.2 dB | 0 | 0 |
| 23 | Locked | QAM256 | 39 | 393000000 Hz | 0.3 dBmV | 45.3 dB | 0 | 0 |
| 24 | Locked | QAM256 | 40 | 399000000 Hz | 0.2 dBmV | 45.2 dB | 0 | 0 |
| 25 | Locked | QAM256 | 41 | 405000000 Hz | 0.2 dBmV | 45.2 dB | 0 | 0 |
| 26 | Locked | QAM256 | 42 | 411000000 Hz | 0.2 dBmV | 45.1 dB | 0 | 0 |
| 27 | Locked | QAM256 | 43 | 417000000 Hz | 0.2 dBmV | 45.2 dB | 0 | 0 |
| 28 | Locked | QAM256 | 44 | 423000000 Hz | 0.2 dBmV | 45.2 dB | 0 | 0 |
| 29 | Locked | QAM256 | 45 | 429000000 Hz | 0.2 dBmV | 45.2 dB | 0 | 0 |
| 30 | Locked | QAM256 | 46 | 435000000 Hz | 0.1 dBmV | 45.1 dB | 0 | 0 |
| 31 | Locked | QAM256 | 47 | 441000000 Hz | 0 dBmV | 45.1 dB | 0 | 0 |
| 32 | Locked | QAM256 | 48 | 447000000 Hz | 0 dBmV | 45.1 dB | 0 | 0 |
Upstream Bonded Channels
| Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power |
| 1 | Locked | ATDMA | 1 | 5120 Ksym/sec | 16900000 Hz | 42.5 dBmV |
| 2 | Locked | ATDMA | 2 | 5120 Ksym/sec | 23500000 Hz | 43 dBmV |
| 3 | Locked | ATDMA | 3 | 5120 Ksym/sec | 29900000 Hz | 43 dBmV |
| 4 | Locked | ATDMA | 4 | 5120 Ksym/sec | 36300000 Hz | 43 dBmV |
| 5 | Locked | ATDMA | 5 | 5120 Ksym/sec | 60000000 Hz | 44 dBmV |
| 6 | Locked | ATDMA | 6 | 5120 Ksym/sec | 67000000 Hz | 44.5 dBmV |
| 7 | Locked | ATDMA | 7 | 5120 Ksym/sec | 74000000 Hz | 45 dBmV |
| 8 | Locked | ATDMA | 8 | 5120 Ksym/sec | 81000000 Hz | 45 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 | Not Locked | 0 | 0 | 0 Hz | 0 dBmV | 0.0 dB | 0 ~ 4095 | 0 | 0 | 0 |
| 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 PowerEnable Extended Upstream Transmit Power
Current System Time:Sat Dec 11 14:06:15 2021System Up Time:16:10:08
- Cox-Me-NitgearDec 11, 2021Aspirant
Here is a snippet of my event log:
Time Priority Description Sat Dec 11 14:10:40 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:02:43 2021 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:02:21 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:02:13 2021 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:02:07 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:02:05 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:02:02 2021 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:02:01 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; Sat Dec 11 14:01:57 2021 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; - FURRYe38Dec 12, 2021Guru - Experienced User
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/- Cox-Me-NitgearDec 12, 2021Aspirant
Thank again Furry. Based on the logs and information in the links you provided it would appear that the problem is NOT related to the modem itself. Cox is implying that the problem is the modem as per DOCSIS tips, T3 timeouts are typically caused by noise on the upstream.
Time Priority Description Sun Dec 12 15:59:42 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:a3:b9:e0;CMTS-MAC=00:29:c2:00:57:92;CM-QOS=1.1;CM-VER=3.1; What a nightmare dealing with Cox.
It will be interesting to see the difference with Panoramic WiFi that we should receive within a couple of days. I feel like we are being taken agvantage of and forced to sign up for something we should not be replacing.