NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
cm500 help
isp whoi i have tell me call netgear netgear tell me to call isp i get runaroun i see on modem lofin page under event log this on 192.168.100.1 under vent logs i see lots of these 2022-2-17...
It helps more if you have the complete logs and the cable connections page.
| 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 | 561000000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Security | Enabled | BPI+ |
| IP Provisioning Mode | Honor MDD | honorMdd(4) |
Downstream Bonded Channels
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Correctables | Uncorrectables |
| 1 | Locked | QAM256 | 1 | 561000000 Hz | -1.1 dBmV | 37.1 dB | 0 | 0 |
| 2 | Locked | QAM256 | 2 | 567000000 Hz | -1.4 dBmV | 38.9 dB | 413 | 0 |
| 3 | Locked | QAM256 | 3 | 573000000 Hz | -0.7 dBmV | 39.3 dB | 195 | 0 |
| 4 | Locked | QAM256 | 4 | 579000000 Hz | -1.5 dBmV | 36.1 dB | 85 | 0 |
| 5 | Locked | QAM256 | 5 | 585000000 Hz | -2.2 dBmV | 37.4 dB | 633 | 1336 |
| 6 | Locked | QAM256 | 6 | 591000000 Hz | -0.8 dBmV | 40.2 dB | 0 | 0 |
| 7 | Locked | QAM256 | 9 | 609000000 Hz | -1.1 dBmV | 39.3 dB | 38 | 0 |
| 8 | Locked | QAM256 | 10 | 615000000 Hz | -1.5 dBmV | 36.7 dB | 3116 | 0 |
| 9 | Locked | QAM256 | 21 | 687000000 Hz | -0.7 dBmV | 39.5 dB | 0 | 0 |
| 10 | Locked | QAM256 | 22 | 693000000 Hz | -0.2 dBmV | 40.9 dB | 0 | 0 |
| 11 | Locked | QAM256 | 23 | 699000000 Hz | 0.1 dBmV | 41.7 dB | 0 | 0 |
| 12 | Locked | QAM256 | 24 | 705000000 Hz | 1.6 dBmV | 42.2 dB | 0 | 0 |
| 13 | Locked | QAM256 | 25 | 711000000 Hz | 1 dBmV | 40.3 dB | 0 | 0 |
| 14 | Locked | QAM256 | 26 | 717000000 Hz | 0.6 dBmV | 37.5 dB | 94 | 0 |
| 15 | Locked | QAM256 | 27 | 723000000 Hz | 1.3 dBmV | 40 dB | 0 | 0 |
| 16 | Locked | QAM256 | 28 | 729000000 Hz | 0.3 dBmV | 40.2 dB | 0 | 0 |
Upstream Bonded Channels
| Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power |
| 1 | Locked | ATDMA | 2 | 5120 Ksym/sec | 24600000 Hz | 50.8 dBmV |
| 2 | Locked | ATDMA | 1 | 2560 Ksym/sec | 18000000 Hz | 51 dBmV |
| 3 | Locked | ATDMA | 3 | 5120 Ksym/sec | 31000000 Hz | 51 dBmV |
| 4 | Locked | ATDMA | 4 | 5120 Ksym/sec | 37400000 Hz | 51 dBmV |
Extended Upstream Transmit Power Enable Extended Upstream Transmit Power
Current System Time:Thu Feb 17 20:30:12 2022
System Up Time:02:52:53
2022-2-17, 20:15:36 Warning (5) MDD message timeout;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-17, 17:37:56 Notice (6) TLV-11 - unrecognized OID;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:33 Notice (6) Honoring MDD; IP provisioning mode = IPv4 1970-1-1, 00:00:27 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:27 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2022-2-17, 17:29:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-17, 17:29:05 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-17, 17:28:59 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:26 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2022-2-17, 11:32:15 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-17, 11:32:14 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-17, 11:32:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-17, 11:07:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-16, 20:12:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-16, 19:09:25 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:28 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:28 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2022-2-15, 17:25:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 17:25:15 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 17:25:15 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 17:24:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 17:23:57 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 17:23:55 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 17:23:53 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 16:27:45 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 16:27:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:26 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:28 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2022-2-15, 16:01:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 16:01:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 16:01:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 15:58:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; 2022-2-15, 15:57:43 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0; Your logs are indicating line issues.
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, bad/old/cheap connectors, or corroded connections. Replace them if you do.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.isp tell me cant sent a tech at all i have wowway in desplaines il tell me to come to netgear since i own modem what i do now?