dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2092
raider1
join:2012-03-08
Oceanside, CA

1 edit

raider1

Member

[CA] SD - Cox Ultimate - Motorola SBG6580

Click for full size
Dear Techs,

I'm trying to resolve consistent disconnects of my Modem/Router. It just times out and goes down frequently.

Time Priority Description
Thu Mar 08 12:17:38 2012 Notice (6) TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 08 12:17:30 2012 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Thu Mar 08 12:17:13 2012 Notice (6) T4 No Station Maint Timeout - Reinitialize MAC...
Thu Mar 08 12:17:13 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Thu Mar 08 12:14:07 2012 Notice (6) TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Wed Mar 07 19:08:36 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Wed Mar 07 17:08:58 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Tue Mar 06 17:08:13 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 06 17:02:50 2012 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 06 17:02:38 2012 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Tue Mar 06 17:02:21 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 06 16:58:03 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Mar 06 16:55:47 2012 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Tue Mar 06 16:55:30 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Sun Mar 04 16:59:07 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 04 16:55:37 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Mar 04 16:55:34 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 04 16:55:12 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Mar 04 16:54:13 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Mar 04 16:54:07 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sun Mar 04 16:53:51 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Sun Mar 04 16:47:58 2012 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Sun Mar 04 16:40:00 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Mar 04 16:31:43 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 04 16:28:40 2012 Critical (3) REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Sat Mar 03 13:22:45 2012 Critical (3) No Ranging Response received - T3 time-out
Sat Mar 03 13:22:38 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sat Mar 03 13:22:20 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Sat Mar 03 13:22:11 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Sat Mar 03 13:22:07 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Sat Mar 03 13:15:09 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Sat Mar 03 11:15:35 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Fri Mar 02 05:01:12 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 05:01:03 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 05:00:57 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 05:00:50 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 05:00:48 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:59:35 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:59:25 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:59:16 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:59:13 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Fri Mar 02 04:55:41 2012 Critical (3) No Ranging Response received - T3 time-out
Fri Mar 02 04:55:34 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:55:18 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:55:16 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:54:22 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:50:29 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:50:28 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:59 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:59 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:55 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:55 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:54 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:54 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:53 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:53 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:52 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:51 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:50 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:50 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:49 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:49 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:48 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:48 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:46 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:46 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:45 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:45 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:44 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:44 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:43 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:43 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:22 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:49:20 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:43 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:42 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:41 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:41 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:40 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:40 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:39 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:39 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:38 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:37 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:36 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:36 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:35 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:35 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:34 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:34 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:33 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:32 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 02 04:47:31 2012 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
m8trix
join:2003-12-24
Chandler, AZ

m8trix

Member

Re: [CA] SD - Cox Ultimate - Motorola SBG8560

what firm ware do you have? and your upstream power is low
raider1
join:2012-03-08
Oceanside, CA

raider1

Member

said by m8trix:

what firm ware do you have? and your upstream power is low

Software Version SBG6580-3.2.1.0-GA-02-249-NOSH

It was different but I had them push me this one after numerous phone calls, but I'm still having issues.

What can I do about my upstream power? Also,

CM IP Address Duration Expires
xx.xxx.xxx.xxx D: 01 H: 00 M: 00 S: 00 Fri Mar 09 12:17:35 2012

12:17 I think that's at least one of the times in the log that shows things getting whack.
m8trix
join:2003-12-24
Chandler, AZ

m8trix

Member

you may need a tech out to correct, a splitter would increase it but leaving a unused port may cause ingress into your connection
, or maybe even a directional coupler
raider1
join:2012-03-08
Oceanside, CA

raider1

Member

said by m8trix:

you may need a tech out to correct, a splitter would increase it but leaving a unused port may cause ingress into your connection
, or maybe even a directional coupler

I have a tech coming out tomorrow morning. I've fought this for awhile now, but I'm finally giving in. I just don't want the tech to come out for no reason. I also don't want the tech to come out here while the internet is working and come to the conclusion that there is no issue.

dvd536
as Mr. Pink as they come
Premium Member
join:2001-04-27
Phoenix, AZ

dvd536

Premium Member

said by raider1:

said by m8trix:

you may need a tech out to correct, a splitter would increase it but leaving a unused port may cause ingress into your connection
, or maybe even a directional coupler

I have a tech coming out tomorrow morning. I've fought this for awhile now, but I'm finally giving in. I just don't want the tech to come out for no reason. I also don't want the tech to come out here while the internet is working and come to the conclusion that there is no issue.

Somehow i'm betting if that moto modem was swapped for a cisco the issues would disappear
m8trix
join:2003-12-24
Chandler, AZ

m8trix

Member

swapping modems not going to fix low levels
raider1
join:2012-03-08
Oceanside, CA

raider1

Member

Click for full size
Cox Tech came out, but apparently there's an issue in the entire area that I'm in.

Anyways, he did some tech wizardry and now this is what my modem reports:
m8trix
join:2003-12-24
Chandler, AZ

m8trix

Member

what did he say was the issue in the area

SHoTTa35
@optonline.net

SHoTTa35 to raider1

Anon

to raider1
Doesn't seem like he did anything as your sending power levels are still 29 for sending, I thought 33 was the lowest it should be. 39 would probably be perfect.

Then again i've seen about 3 people post now (using Arris modems too) and their power levels are 33.7 and 32 and now yours. I don't remember their locations but it's all similar problems.
raider1
join:2012-03-08
Oceanside, CA

raider1

Member

Click for full size
He said there was an issue with the node.

However, he went through all the wiring and found rat chew and other wire damage throughout.

He did repairs and this is my stats now:
raider1

raider1

Member

Time Priority Description
Fri Mar 09 14:45:50 2012 Notice (6) TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Fri Mar 09 14:45:44 2012 Critical (3) DHCP FAILED - Request sent, No response;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 09 14:45:25 2012 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.0;CM-VER=3.0;
Fri Mar 09 14:45:10 2012 Notice (6) T4 No Station Maint Timeout - Reinitialize MAC...
Fri Mar 09 14:45:10 2012 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
Fri Mar 09 14:42:03 2012 Notice (6) TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:26:99:89:f2:ce;CM-QOS=1.1;CM-VER=3.0;
-----------------------------------------------------

Yet again. At this point, I am willing to try a different modem, but I need recommendations.

My requirements are I need hardline for my computer and wireless for the rest of the house which is why I use the one I have...but I don't know now...

dvd536
as Mr. Pink as they come
Premium Member
join:2001-04-27
Phoenix, AZ

dvd536 to m8trix

Premium Member

to m8trix
said by m8trix:

swapping modems not going to fix low levels

His downstream is in spec.
if hes got clean upstream, the modem doesn't have to shout to be heard by the CMTS.

Jameson
Premium Member
join:2004-05-28
united state

Jameson

Premium Member

Don't feel bad, I have Ultimate and I only see 8Mbps down at night. Welcome to the Cox club.