Forum Discussion

g-naps's avatar
g-naps
New Contributor

SB 6141 modem issues

For about the last 2 weeks Ive had to manually reset my modem, SB6141, in the morning. The connectivity is fine during the day but something happens between around 12am and 6am. 

Firmware is at  SB_KOMODO-1.0.6.14-SCM01-NOSH

heres the signal:

DownstreamBonding Channel Value
Channel ID 1  2  3  4  9  10  11  12 
Frequency 813000000 Hz  819000000 Hz  825000000 Hz  831000000 Hz  861000000 Hz  867000000 Hz  873000000 Hz  879000000 Hz 
Signal to Noise Ratio 37 dB  37 dB  37 dB  37 dB  38 dB  39 dB  38 dB  37 dB 
Downstream Modulation QAM256  QAM256  QAM256  QAM256  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
7 dBmV   7 dBmV   8 dBmV   7 dBmV   7 dBmV   7 dBmV   6 dBmV   6 dBmV  

UpstreamBonding Channel Value
Channel ID 2  1  3  4 
Frequency 32200000 Hz  25800000 Hz  38600000 Hz  17600000 Hz 
Ranging Service ID 92  92  92  92 
Symbol Rate 5.120 Msym/sec  5.120 Msym/sec  5.120 Msym/sec  2.560 Msym/sec 
Power Level 35 dBmV  35 dBmV  35 dBmV  35 dBmV 
Upstream Modulation [3] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 		 [3] QPSK
[2] 16QAM
[3] 64QAM
 
Ranging Status Success  Success  Success  Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 1  2  3  4  9  10  11  12 
Total Unerrored Codewords 7322267  6615733  6633671  6641945  6610581  6612899  6613975  6651152 
Total Correctable Codewords 0  240  0  0  49  12  18  20 
Total Uncorrectable Codewords 1440  2404  1511  1418  1496  1521  1516  1514 

Jul 31 2016 08:09:49 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2016 08:09:49 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2016 07:50:53 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 30 2016 08:15:11 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 30 2016 08:15:11 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 29 2016 11:03:02 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 29 2016 11:03:02 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 28 2016 12:04:59 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 28 2016 12:04:59 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 27 2016 22:51:03 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 27 2016 10:54:26 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jul 27 2016 10:54:26 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

connection issues
connection issues T3 errors Timeout
connectivity

4 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • AllenP's avatar
    AllenP
    Valued Contributor

    Are the "Cable Modem Reboot" entries in you log due to you restarting the modem or is it sensing a power issue?  Is the modem plugged directly into a wall outlet or into a power strip / surge suppressor?  If a power strip, can you test plugged directly into an outlet?

    What are the symptoms in the AM when you have to reboot?  Are the modem lights normal or do they show a problem?  Are you connected from the modem to a router?  What model?  Can you test with a computer wired directly to the modem, bypassing the router?  Just trying to narrow down the issue with all these questions/tests.  Thanks

  • Becky's avatar
    Becky
    Moderator
    Hi G-naps,

    My first thought mirrors the direction in which AllenP is headed. Does your modem connect to a surge protector or power strip? If so, connect it to a wall outlet to see if it makes any difference in the connectivity issues you're experiencing. If you don't reset your modem every morning, what happens when you try to open a web page?

  • g-naps's avatar
    g-naps
    New Contributor

    The cable modem reboots are from me manually rebooting the modem. The modem and router are plugged into a surge protector. The symptom is no internet connectivity whether it is a wireless or wired connection to my router.  The modem is connected to a netgear ac1900 router. I only reboot the modem and leave the router powered on. This setup has been rock solid since I had the latest firmware pushed down to the modem last year. Nothing has changed in my setup, ie no router updates or additional devices.

    I havent looked at the lights on the modem prior to reboot since I figured the logs would give a better idea of whats happening with the modem.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @g-naps

    In the interest of being thorough I'd also suggest testing without the router just to be sure something else is going on. Rebooting the modem also resets the Ethernet interface on the router which may be masking some other problem that could be going on.