Chrono558's profile

New Contributor

 • 

1 Message

Closed

Service disruption in Rogers, AR

For the past couple of days, My Internet (Preferred Tier) has been having sporadic outages for varying lengths of time.  I've reviewed both signal levels and logs for the cable modem which I'll post below. Modem is a Motorola SB6121 running firmware SB_KOMODO-1.0.6.12-SCM00-NOSH

Downstream Bonding Channel Value
Channel ID 3  4  11  12 
Frequency 807000000 Hz  813000000 Hz  831000000 Hz  837000000 Hz 
Signal to Noise Ratio 37 dB  37 dB  37 dB  37 dB 
Downstream Modulation QAM256  QAM256  QAM256  QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-5 dBmV   -5 dBmV   -7 dBmV   -7 dBmV  
Upstream Bonding Channel Value
Channel ID 2  3  4 
Frequency 23700000 Hz  28700000 Hz  35300000 Hz 
Ranging Service ID 1151  1151  1151 
Symbol Rate 2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
Power Level 40 dBmV  39 dBmV  41 dBmV 
Upstream Modulation [3] 16QAM
[3] 64QAM
 
[3] 16QAM
[3] 64QAM
 
[3] 16QAM
[3] 64QAM
 
Ranging Status Success  Success  Success 

Best I can tell, my signal levels are fine.  Downstream power is a little off, but should still be well within the realm of normal.  I've checked the signal levels throughout different parts of the day and they all stay about the same. 

TimePriorityCodeMessage
Nov 14 2013 12:07:56 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 14 2013 09:24:03 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 14 2013 09:24:03 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:55 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=XXX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Nov 14 2013 09:22:40 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 14 2013 09:21:49 5-Warning T202.0 Lost MDD Timeout;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 14 2013 09:21:25 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 13 2013 23:19:26 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 13 2013 21:43:59 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 13 2013 21:43:59 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 13 2013 21:43:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 13 2013 01:44:58 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 13 2013 01:44:58 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 13 2013 01:44:57 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 12 2013 09:38:10 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 12 2013 09:27:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 12 2013 09:26:58 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XXX; CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 12 2013 09:26:58 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;
Nov 12 2013 09:26:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XXX;CMTS-MAC=XXX;CM-QOS=1.1;CM-VER=3.0;

I'm not sure if this is a problem on my end or if there is still some work being done in the area from a bigger outage that happened over the weekend.  Would it be possible for a Cox Technician to check this?  Thanks.

Former Moderator

 • 

7.1K Messages

The levels largely look good from this end.  Can you try without the router to see if there is any difference?  Do you notice any change in the modem lights when the problems occur?

Related Content

Recent Discussions