cm500 help

Question

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, 17:37:56

Notice (6)

70-1-1, 00:00:27

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=

whats going on thansk ray isp sed call netgear netgear tell me call isp

Message 1 of 3

2022-2-17, 17:37:56

Notice (6)

TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=

Message 2 of 3

whatg i do to get isp to fiox it want to charge me tell me cant help since i own modem not its a CM500-100NAS what i do thansk ray toth i rebooted modem no help what eles i do thansk took cisco ccna in college also

raymondjtoth · Answer

i mean i have a CM500-100NAS &nbsp; sorry typoed first time

plemans · Answer

It helps more if you have the complete logs and the cable connections page.&nbsp;

raymondjtoth · Answer

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.Starting Frequency &nbsp;Startup Procedure Procedure Status Comment Acquire Downstream Channel561000000 HzLockedConnectivity StateOKOperationalBoot StateOKOperationalSecurityEnabledBPI+IP Provisioning ModeHonor MDDhonorMdd(4)&nbsp;Downstream Bonded ChannelsChannel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1LockedQAM2561561000000 Hz-1.1 dBmV37.1 dB002LockedQAM2562567000000 Hz-1.4 dBmV38.9 dB41303LockedQAM2563573000000 Hz-0.7 dBmV39.3 dB19504LockedQAM2564579000000 Hz-1.5 dBmV36.1 dB8505LockedQAM2565585000000 Hz-2.2 dBmV37.4 dB63313366LockedQAM2566591000000 Hz-0.8 dBmV40.2 dB007LockedQAM2569609000000 Hz-1.1 dBmV39.3 dB3808LockedQAM25610615000000 Hz-1.5 dBmV36.7 dB311609LockedQAM25621687000000 Hz-0.7 dBmV39.5 dB0010LockedQAM25622693000000 Hz-0.2 dBmV40.9 dB0011LockedQAM25623699000000 Hz0.1 dBmV41.7 dB0012LockedQAM25624705000000 Hz1.6 dBmV42.2 dB0013LockedQAM25625711000000 Hz1 dBmV40.3 dB0014LockedQAM25626717000000 Hz0.6 dBmV37.5 dB94015LockedQAM25627723000000 Hz1.3 dBmV40 dB0016LockedQAM25628729000000 Hz0.3 dBmV40.2 dB00&nbsp;Upstream Bonded ChannelsChannel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1LockedATDMA25120 Ksym/sec24600000 Hz50.8 dBmV2LockedATDMA12560 Ksym/sec18000000 Hz51 dBmV3LockedATDMA35120 Ksym/sec31000000 Hz51 dBmV4LockedATDMA45120 Ksym/sec37400000 Hz51 dBmV&nbsp;Extended Upstream Transmit Power Enable Extended Upstream Transmit Power&nbsp;Current System Time:Thu Feb 17 20:30:12 2022&nbsp;&nbsp;System Up Time:02:52:53

raymondjtoth · Answer

2022-2-17, 20:15:36Warning (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:56Notice (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:33Notice (6)Honoring MDD; IP provisioning mode = IPv41970-1-1, 00:00:27Critical (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:22Critical (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:27Critical (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:22Critical (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:11Critical (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:05Critical (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:59Critical (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:26Critical (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:21Critical (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:15Critical (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:14Critical (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:09Critical (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:35Critical (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:04Critical (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:25Critical (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:28Critical (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:22Critical (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:28Critical (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:22Critical (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:15Critical (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:15Critical (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:15Critical (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:06Critical (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:57Critical (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:55Critical (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:53Critical (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:45Critical (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:41Critical (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:26Critical (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:21Critical (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:28Critical (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:22Critical (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:34Critical (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:18Critical (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:13Critical (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:24Critical (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:43Critical (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;

plemans · Answer

Your logs are indicating line issues.&nbsp;
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.

Forum Discussion

cm500 help