Forum Discussion

LowTide76's avatar
LowTide76
New Contributor

SB6120 Issues

I am starting to have to reboot my modem several times a day.  Details below.  Is this the latest firmware?  Based on the logs, see any issues?  TIA

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.16-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Serial Number: 317001023704255005040011
Firmware Build Time: Feb 16 2016 11:28:04

TimePriorityCodeMessage
Oct 18 2016 15:07:21 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Oct 18 2016 15:07:21 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:23 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 18 2016 13:22:36 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Oct 18 2016 07:59:58 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Oct 18 2016 07:59:58 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 16 2016 10:28:15 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Oct 16 2016 10:28:15 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Oct 14 2016 16:11:54 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2016 08:22:28 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2016 08:22:28 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 01 2016 17:21:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Sep 29 2016 02:04:15 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
Sep 29 2016 02:04:15 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f5:b5:e3;CMTS-MAC=00:14:f1:e5:a5:e5;CM-QOS=1.1;CM-VER=3.0;
connection issues
connection issues T3 errors Timeout

3 Replies

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

    Signal information

    information about the current upstream and downstream signal status of your Cable Modem.

    DownstreamBonding Channel Value
    Channel ID 178  177  179  180 
    Frequency 837000000 Hz  831000000 Hz  843000000 Hz  849000000 Hz 
    Signal to Noise Ratio 37 dB  37 dB  37 dB  38 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
    		13 dBmV   13 dBmV   13 dBmV   14 dBmV  

    UpstreamBonding Channel Value
    Channel ID 2  1  3  4 
    Frequency 24000000 Hz  17600000 Hz  30400000 Hz  36800000 Hz 
    Ranging Service ID 34  34  34  34 
    Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
    Power Level 43 dBmV  43 dBmV  43 dBmV  43 dBmV 
    Upstream Modulation [3] 16QAM
    [3] 64QAM
         		 [3] QPSK
    [2] 16QAM
    [3] 64QAM
         		 [3] 16QAM
    [3] 64QAM
         		 [3] 16QAM
    [3] 64QAM
     
    Ranging Status Success  Success  Success  Success 

    Signal Stats (Codewords)Bonding Channel Value
    Channel ID 178  177  179  180 
    Total Unerrored Codewords 21779855  21780064  21780155  21780421 
    Total Correctable Codewords 14  1  0  0 
    Total Uncorrectable Codewords 1557  1467  1515  1388 
  • grymwulf's avatar
    grymwulf
    Contributor II

    That does look like the proper firmware build, they just released a new one (appears compiled in Feb, but cleared from testing in Sep/Oct?).

    Reboots on the 18th x2, 16th x1, 3rd x1 etc - after each reboot you normally will have at least 1 t3/t4 timeout, because the modem isn't connected immediately.  There are no entries (time-wise) immediately before the 'Reboot due to power reset' - so it doesn't look like a problem that the modem logs.

    DS: Power level is at the upper end but still within acceptable limits considering the SNR and lack of errors

    US: Well within spec

    The question becomes what type of disconnect?

    Process - determine where in the route the issue pops up -

    1. When next it drops out, see if you can browse to 192.168.100.1 (where you got what you posted), if it's unreachable the problem occurs locally, somewhere between PC and modem.
    2. If the modem is reachable, grab a shot of signal levels at that point and the log
    3. Ping 8.8.8.8 or 8.8.4.4 - if you can reach those you are connected to the internet, it might be DNS
    4. Ping google.com - if you can reach it, hey the internet is working, it might be browser based (proxy/dns hijack?).  If you can't reach google.com it's a DNS issue, try setting your router to over-ride DNS and use 8.8.8.8 or 8.8.4.4

  • LowTide76's avatar
    LowTide76
    New Contributor

    OK, will do.  I do notice that when I go into the router it tells me there is no IP address and no internet.  So when I reboot the modem all is good.  I will run through the steps.

    BTW, I am using those DNS servers in a manual override for my IP v4 settings, router is actually giving out Open DNS to other DHCP clients (kids so it is locked down)  other clients and my computer still have same issue.

    Let me run through steps next time it happens and report back.