CatB's profile

New Contributor

 • 

5 Messages

Closed

SB6121 Rebooting All Day

I posted a couple weeks back about dropped connections/modem reboots, and, after replacing the splitter, things got a little better.  However, with the rain, it's been something terrible.  The modem is fairly new -- about 4 mos old, but, I was having drop issues with the old 5101, just not as often -- maybe twice a week as opposed to a couple times a day (at least until today when it's been REALLY bad).

Is it possible I have a bad line somewhere and it really shows up with the rain?  If so, what is the best way to resolve the issue?  Below is a log of today's numerous reboots:

Cable Modem
StatusSignalAddressesConfigurationLogsOpen SourceHelp
This page displays detailed information intended for use by an authorized Motorola Corporation Cable Modem technician.

TimePriorityCodeMessage
Mar 23 2012 17:27:47 5-Warning T202.0 Lost MDD Timeout;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 17:27:45 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 17:21:15 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:34 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 17:20:21 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 17:19:54 4-Error C401.0 DCC-ACK not received;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 17:19:48 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 17:10:07 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 17:00:38 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 16:52:47 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:32 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 16:51:56 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 16:51:26 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 16:36:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 16:36:38 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Mar 23 2012 16:33:47 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:35 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:13:5f:03:50:54;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=74:56:12:2a:e8:3d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Status | Signal | Addresses | Configuration | Logs | Open Source | Help

© Copyright 1997-2008

Former Moderator

 • 

7.1K Messages

I sent you a private message asking for more information.

New Contributor

 • 

4 Messages

Cox Phone Support should be able to ping your router and also see drops and reboots.  A Field Tech would confirm that.  Ask if there is any special software being added to your region?  Have the Field Tech check the neighborhood tap and the other homes on that tap to see if other users are seeing failures.  Then move towards the home exterior box to cable modem connection.  

Related Content

Recent Discussions