NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM2000 - upstream Amber light - slow/dropping connection
CM2000 Modem
Firmware Version V8.01.02
Nighthawk AX6 6-Stream AX5400 WiFi Router
Xfinity - Comcast - gig service
Noob Level Knowledge **
Been running this setup for a year or two with fluctuating connection speeds
and I believe most my issues may be line or service related
but was hoping for opinions from those in the know before I take on Xfinity
Just recently got a solid Amber colored upstream light so I logged in and saw this:
| Tue May 09 20:50:00 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:38 2023 | (Warning (5)) | TCS Partial Service;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:38 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:27 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:26 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:21 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:20 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:17 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:17 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:14 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:14 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:04 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:49:03 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:54 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:54 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:53 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:52 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:51 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:50 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:47 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:46 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:46 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:45 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:45 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:44 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:42 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:42 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:42 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:41 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:40 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:39 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:48:39 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:38:14 2023 | (Warning (5)) | TCS Partial Service;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:38:14 2023 | (Warning (5)) | RCS Partial Service;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:38:12 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:38:08 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:38:08 2023 | (Warning (5)) | TCS Partial Service;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; | Tue May 09 20:38:07 2023 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=38:94:ed:09:f3:88;CMTS-MAC=00:90:f0:2e:02:00;CM-QOS=1.1;CM-VER=3.1; What does it all mean ? Thank you |
4 Replies
Original post didn't come out right
Startup Procedure Procedure Status Comment Acquire Downstream Channel 675000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD IPv6 only Downstream Bonded Channels (Partial Service) Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 44 675000000 Hz -5.7 dBmV 41.3 dB 0 0 2 Locked QAM256 13 489000000 Hz -4.6 dBmV 42.7 dB 0 0 3 Locked QAM256 14 495000000 Hz -4.6 dBmV 42.7 dB 0 0 4 Locked QAM256 15 501000000 Hz -4.8 dBmV 28.7 dB 207449 0 5 Not Locked Unknown 16 507000000 Hz 0.0 dBmV 0.0 dB 0 0 6 Locked QAM256 17 513000000 Hz -5.2 dBmV 32.2 dB 1614112 303930 7 Locked QAM256 18 519000000 Hz -5.4 dBmV 36.4 dB 0 0 8 Locked QAM256 19 525000000 Hz -5.4 dBmV 37.7 dB 0 0 9 Locked QAM256 20 531000000 Hz -5.4 dBmV 41.0 dB 0 0 10 Locked QAM256 21 537000000 Hz -5.2 dBmV 41.6 dB 0 0 11 Locked QAM256 22 543000000 Hz -5.0 dBmV 42.4 dB 0 0 12 Locked QAM256 23 549000000 Hz -4.9 dBmV 42.5 dB 0 0 13 Locked QAM256 24 555000000 Hz -4.9 dBmV 42.3 dB 0 0 14 Locked QAM256 25 561000000 Hz -5.0 dBmV 42.1 dB 0 0 15 Locked QAM256 26 567000000 Hz -5.0 dBmV 41.9 dB 0 0 16 Locked QAM256 27 573000000 Hz -5.2 dBmV 41.9 dB 0 0 17 Locked QAM256 28 579000000 Hz -5.3 dBmV 41.9 dB 0 0 18 Locked QAM256 29 585000000 Hz -5.4 dBmV 42.0 dB 0 0 19 Locked QAM256 30 591000000 Hz -5.4 dBmV 42.0 dB 0 0 20 Locked QAM256 31 597000000 Hz -5.5 dBmV 39.1 dB 0 0 21 Locked QAM256 32 603000000 Hz -5.5 dBmV 29.1 dB 227893 0 22 Locked QAM256 33 609000000 Hz -5.7 dBmV 37.3 dB 0 0 23 Locked QAM256 34 615000000 Hz -5.7 dBmV 41.8 dB 0 0 24 Locked QAM256 35 621000000 Hz -5.7 dBmV 41.7 dB 0 0 25 Locked QAM256 36 627000000 Hz -5.8 dBmV 41.5 dB 0 0 26 Locked QAM256 37 633000000 Hz -5.8 dBmV 41.2 dB 0 0 27 Locked QAM256 38 639000000 Hz -5.9 dBmV 41.7 dB 0 0 28 Locked QAM256 39 645000000 Hz -5.8 dBmV 41.8 dB 0 0 29 Locked QAM256 40 651000000 Hz -6.0 dBmV 41.7 dB 0 0 30 Locked QAM256 41 657000000 Hz -5.8 dBmV 41.8 dB 0 0 31 Locked QAM256 42 663000000 Hz -5.8 dBmV 41.8 dB 0 0 32 Locked QAM256 43 669000000 Hz -5.9 dBmV 41.7 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 53.0 dBmV 2 Not Locked Unknown 0 0 0 0.0 dBmV 3 Not Locked Unknown 0 0 0 0.0 dBmV 4 Not Locked Unknown 0 0 0 0.0 dBmV 5 Not Locked Unknown 0 0 0 0.0 dBmV 6 Not Locked Unknown 0 0 0 0.0 dBmV 7 Not Locked Unknown 0 0 0 0.0 dBmV 8 Not Locked Unknown 0 0 0 0.0 dBmV Downstream OFDM Channels Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1 Locked 0 ,1 ,2 ,3 193 957000000 Hz -8.72 dBmV 38.1 dB 148 ~ 3947 86779531 58860179 954 2 Not Locked 0 0 0 Hz 0 dBmV 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 Current System Time:Tue May 09 23:12:24 2023 System Up Time:01:29:57 Power levels are kinda low but with in spec. https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
You have Correcables and Un-correctables on some channels that should be zero's like the other channels.
Any Criticals, Errors or warnings seen in the Event logs needs to be reviewed and resolved by the ISP.
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/Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended.
What is the brand and model of the host wifi router connected to the modem?Thank you for reply.
My router is
Nighthawk AX6 6-Stream AX5400
This site you directed me to is an amazing resource of information.
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
Trouble shooting and testing today. I'll follow up with findings.
Thanks again
Let us know how it goes...
