Visitor
•
5 Messages
SYNC Timing Synchronization failure - Loss of Sync
Over the past week my internet connection has been dropping and my modem (Netgear Nighthawk CM2000) has been rebooting itself. The event log shows "SYNC Timing Synchronization failure - Loss of Sync". Below is the log...
| Wed Mar 05 15:30:44 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| Wed Mar 05 15:27:54 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.; |
| Wed Mar 05 15:24:41 2025 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"]; |
| Wed Mar 05 15:24:34 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; |
| Wed Mar 05 15:24:33 2025 | (Notice (6)) | TLV-11 - unrecognized OID; |
| Wed Mar 05 15:24:24 2025 | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
| Wed Mar 05 15:24:12 2025 | (Warning (5)) | ToD request sent - No Response received; |
| Wed Mar 05 15:24:12 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 15:24:12 2025 | (Critical (3)) | No Ranging Response received - T3 time-out; |
| Wed Mar 05 15:24:10 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 15:24:10 2025 | (Critical (3)) | No Ranging Response received - T3 time-out; |
| Wed Mar 05 15:24:05 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 15:23:12 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
| Wed Mar 05 14:21:42 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; |
| Wed Mar 05 14:14:04 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; |
| Wed Mar 05 14:05:51 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; |
| Wed Mar 05 14:05:50 2025 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=[Edited: "Personal Information"]; |
| Wed Mar 05 14:05:41 2025 | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
| Wed Mar 05 14:05:30 2025 | (Warning (5)) | ToD request sent - No Response received; |
| Wed Mar 05 14:05:30 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 14:02:19 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; |
| Wed Mar 05 14:01:43 2025 | (Critical (3)) | No Ranging Response received - T3 time-out; |
| Wed Mar 05 14:01:38 2025 | (Critical (3)) | SYNC Timing Synchronization failure - Loss of Sync; |
| Wed Mar 05 14:01:13 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; |
| Wed Mar 05 14:00:50 2025 | (Critical (3)) | No Ranging Response received - T3 time-out; |
| Wed Mar 05 14:00:41 2025 | (Critical (3)) | SYNC Timing Synchronization failure - Loss of Sync; |
| Wed Mar 05 13:53:32 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; |
| Wed Mar 05 13:48:22 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; |
| Wed Mar 05 13:11:15 2025 | (Notice (6)) | DS profile assignment change. DS |
| Wed Mar 05 13:11:14 2025 | (Notice (6)) | TLV-11 - unrecognized OID; |
| Wed Mar 05 13:11:05 2025 | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
| Wed Mar 05 13:10:53 2025 | (Warning (5)) | ToD request sent - No Response received; |
| Wed Mar 05 13:10:53 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 13:10:53 2025 | (Critical (3)) | No Ranging Response received - T3 time-out; |
| Wed Mar 05 13:10:53 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 13:10:53 2025 | (Critical (3)) | No Ranging Response received - T3 time-out; |
| Wed Mar 05 13:10:51 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 13:10:50 2025 | (Critical (3)) | No Ranging Response received - T3 time-out; |
| Wed Mar 05 13:10:49 2025 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; |
| Wed Mar 05 13:09:53 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out; |
And below are my downstream and upstream channels...
| Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
| Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Any help would be appreciated. I do a lot of my work online and it's near impossible to get anything done when my connection keeps going down. Thank you.
EG
Expert
•
108.9K Messages
3 days ago
This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless.
The upstream power is a bit on the high side and it may be intermittently fluctuating even higher to out of spec levels. And there are a fairly large number of uncorrectable bit errors. Even more than the corrected ones, and that shouldn't be. There may be some spurious noise leaking into the line(s) somewhere.That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
(edited)
4
0
EG
Expert
•
108.9K Messages
3 days ago
@bh535
Please redact all of the CM MAC and the CMTS MAC addresses from your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publicly. It flagged your post as "Private".
(edited)
0
0