- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
CM500 Cable Modem Downstream Constantly Flashing Green
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CM500 Cable Modem Downstream Constantly Flashing Green
My Modem Details:
|
My Issues
For the last week I have noticed download speeds have been a little troublesome.
I browsed some discussions here and found people posting their modems logs, so i thought I'd take a look at mine and i see CRITICAL and WARNING everywhere.
I have no idea what the language means so i felt posting here was the best solution to hopefully rectifying why the downstream light keeps blinking green
Modem Logs
2021-9-12, 14:52:57 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 14:52:56 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 14:01:25 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 14:01:06 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 13:54:37 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 13:54:33 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 12:50:08 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 12:50:04 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 12:38:11 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 12:36:44 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 11:38:20 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 11:38:08 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 11:14:11 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 11:13:59 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 11:08:36 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 11:08:24 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 10:42:57 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 10:42:54 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 10:32:06 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 10:31:33 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 07:05:30 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 07:05:29 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 05:39:21 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 05:39:12 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 00:45:22 | Warning (5) | MDD message timeout;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-9-12, 00:44:32 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
1970-1-1, 00:00:30 | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
1970-1-1, 00:00:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:00:00:00:00:00;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:18:35:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:31 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;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:18:35:bc;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:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;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:18:35:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:33 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
2021-5-26, 01:47:22 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.0;CM-VER=3.0; |
2021-5-26, 01:47:12 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:a6:7e:18:35:bc;CMTS-MAC=00:01:5c:79:c6:4f;CM-QOS=1.1;CM-VER=3.0; |
2021-5-26, 01:47:11 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:18:35:bc;CMTS |
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 Cable Modem Downstream Constantly Flashing Green
Your logs are indicating line issues.
do you have a screen snip of the cable connections page?
Check for splitters, signal attenuators, and amplifiers in line. Remove them if you do.
check the line for kinks, damage, old/loose/bad/corroded connections and replace them if needed.
I'd move the modem to right where the coax enters the home and connect it there.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 Cable Modem Downstream Constantly Flashing Green
After checking the cables I find no erosion ordamaged cables, and I do not have any splitters, signal attenuators, and amplifiers.
the modem is as close to the coax entry point as physically possible.
Could there be a damaged line outside?
I speed test and i get acceptable speeds yet sometimes a website on my desktop will show a DNS failed page buit then within seconds suddenly appears to load the page....
I have attached a screen capture of the connections page
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 Cable Modem Downstream Constantly Flashing Green
For some reason the attached image didn't appear with my reply.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 Cable Modem Downstream Constantly Flashing Green
your cable connections page looks pretty good.
What router do you have the modem connected to?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 Cable Modem Downstream Constantly Flashing Green
I have an Archer A6 https://www.tp-link.com/us/home-networking/wifi-router/archer-a6/v2.8/
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 Cable Modem Downstream Constantly Flashing Green
The signal looks good from the quick snapshot that page loads. But your logs indicate the power is going in/out of spec.
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more