Modem_Resets_It
8 years agoNew Contributor
Solved
Modem Resets itself all the time
Hello,
Our internet is dodgy at best. If we have 4 home devices on it, one or multiple start to lag tremendously. Also, the modem goes through spurts where it just resets itself over and over again.
I erased all of our MAC Addresses, but I posted the log below. With my educational and professional background, it looks like the signal is not coming from Cox like it should. The signal is being lost somewhere. Any thought on what to do or look for? And, no, there are no splitters. There is a cable from the wall to the modem. We have 2 ethernet cables coming from the back of the modem going to 2 computers. Everything else is on WIFI.
Time | Priority | Description |
Thu Jun 09 20:05:01 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC;CM-QOS=1.1;CM-VER=3.0; |
Thu Jun 09 20:04:18 2016 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 07 12:25:16 2016 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=:d0;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 07 12:24:16 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=8;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:24:02 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:22:09 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:22:08 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:19:11 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:19:10 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:18:54 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:18:53 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:18:07 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:18:06 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:17:43 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:17:41 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:17:37 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:17:36 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:16:50 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:16:49 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:15:47 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:15:45 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:15:18 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:15:17 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:14:45 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:14:44 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:14:35 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:14:33 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:14:29 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 07 12:14:28 2016 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1 |
Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv4 |
Time Not Established | Notice (6) | WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT |
- @Modem Resets Itself All the Time
This would suggest there is a signal or equipment problem somewhere. If there are no splitters you could try and see if a different outlet helps. Beyond that it may be time to see about getting a tech out to take a look.