Having issues with your Motorola SB6121? Please post here.

i-am-nerdburg · ‎06-27-2009

There have been a lot of reports recently of the Motorola SB6121 randomly losing connection. It's possible that a recent firmware upgrade is not playing nice. You can help Comcast determine if there is a problem and the nature of the problem.

If you have an SB6121 that is losing its connection please post:

Your signal levels: http://192.168.100.1/cmSignal.htm

Your error logs: http://192.168.100.1/cmLogs.htm

Your firmware information: http://192.168.100.1/cmHelp.htm

Thank you for your help!

------------

Connection and trouble shooting tips (How to check signal levels.) . Info you should post to get help.
The opinions expressed here are my own and are not sanctioned by my employer.

bobcali · ‎08-02-2012

Thanks for trying to help.

I'm having exactly the same problem since last Friday and nothing had changed on my end. I've read in these forums that Comcast finally pushed a firmware upgrade for the SB6121 and there are lots of similar problems including the modem status now shows at "offline" even though it is connected. My firmware version info:

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number: xxxxxxxxxxxxxxxxxxxxxx
Firmware Build Time: Apr 17 2012 15:09:37

I contacted Comcast and the tech remotely reset it several times but did not solve anything.

Here is the log page with all of the same errors:

Aug 02 2012 06:41:08 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:39:01 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:38:38 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:10:08 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:10:04 5-Warning U103.0 Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:10:04 5-Warning U102.0 TCS Partial Service;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:09:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:09:03 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 06:09:03 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;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=cc:7d:37:72:fd:db;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

My signal info seems to look OK:

This page provides information about the current upstream and downstream signal status of your Cable Modem.Channel ID 1 2 4 8 Frequency 705000000 Hz 717000000 Hz 729000000 Hz 753000000 Hz Signal to Noise Ratio 37 dB 37 dB 37 dB 36 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 4 dBmV 5 dBmV 5 dBmV 5 dBmV

Upstream Bonding Channel Value Channel ID 3 1 2 Frequency 37000000 Hz 25300000 Hz 30600000 Hz Ranging Service ID 7780 7780 7780 Symbol Rate 5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec Power Level 39 dBmV 37 dBmV 38 dBmV Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
[3] QPSK
[3] 64QAM
Ranging Status Success Success T4 TimeOut

Signal Stats (Codewords) Bonding Channel Value Channel ID 1 2 4 8 Total Unerrored Codewords 93038539 92317849 92317678 92318031 Total Correctable Codewords 12 3 0 1 Total Uncorrectable Codewords 633 581 587 561

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=cc:7d:37:72:fd:db;CMTS-MAC=00:01:5c:23:c1:51;CM-QOS=1.1;CM-VER=3.0;

0 days 0h:30m:57s

PlaneWryter · ‎08-02-2012

After wasting hours & hours trying to debug this problem (including two calls to Comcast, 1 call to Apple, replacing every Ethernet cable, replacing my router, bypassing the router altogether (direct connect to SB6121)...buying a new SB6121...and testing the direction connection with three computers (2 Macs with Mountain Lion and 1 WinTel machine running Win7), there is compelling evidence of a systematic issue with the SB6121.

On all three machines--when direct connected, or connected via one of two routers (1 Apple Time Capsule and 1 Netgear WNDR3700v2)--the internet will go up-and-down. Sometimes up for an hour...sometimes up-and-down 3 times in ~2 minutes.

Would a knowledgable Comcast employee please investigate? While the front-line 800-COMCAST folks try to help...this problem is considerably beyond their scope.

Please help!

Here's my data:

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number: 359079213726547401012019
Firmware Build Time: Apr 17 2012 15:09:37

Aug 02 2012 09:18:00 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 09:17:59 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;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=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;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=94:cc:b9:18:f0:a9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 07:32:57 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 04:37:01 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 19:54:07 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 19:54:07 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;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=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 19:00:58 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 18:36:11 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 18:36:11 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;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=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from SNMP ;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 18:30:43 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 18:30:43 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;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=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from shell ;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 01 2012 18:29:38 6-Notice E112.0 SW download Successful - Via Config file

Downstream Bonding Channel Value Channel ID 65 66 67 68 Frequency 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz Signal to Noise Ratio 38 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 8 dBmV 8 dBmV 8 dBmV 8 dBmV

Upstream Bonding Channel Value Channel ID 1 2 3 Frequency 30600000 Hz 37000000 Hz 25300000 Hz Ranging Service ID 7612 7612 7612 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level 32 dBmV 32 dBmV 32 dBmV Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
Ranging Status Success Success Success

Signal Stats (Codewords) Bonding Channel Value Channel ID 65 66 67 68 Total Unerrored Codewords 61380008 60387369 60387635 60387726 Total Correctable Codewords 0 1 1 0 Total Uncorrectable Codewords 503 609 497 554

Paul858 · ‎08-02-2012

Yep, having this issue with my SB6121 as well. Here are my stats http://i.imgur.com/xUkaN.jpg, firmware http://i.imgur.com/DnQTg.jpg, and logs http://i.imgur.com/PercV.jpg.

Intermittent hang-ups for about 5 mins, nothing resolves it except waiting.

I haven't updated the firm-ware on the modem though (or is that automatic?)

SteveLiebler · ‎08-02-2012

I am having the same problems - It first started on Sunday 7/29 with my SB6120. It got so bad that on Tuesday, I went out and bought a new router and a new cable modem - the SB6121.

Now it's Thursday and, just as I was expecting, the connection went flaky again. Based on a four day observation, it seems to happen around 13:00 - 13:30 EDT. Coincidence?

I recycled the modem by unplugging it and powering it back on. After getting a connection, I noticed that the connection was extremely slow. This time I took a look at the modem status page at 192.168.100.1 and here is what I found:

https://dl.dropbox.com/u/47239060/Comcast/6121-status.PNG <--Slow connection
https://dl.dropbox.com/u/47239060/Comcast/6121-signal.PNG <--Slow connection
https://dl.dropbox.com/u/47239060/Comcast/6121-config.PNG <--Slow connection

I rebooted the modem until I got a "good" and "fast" connection and here is what the modem says about itself:

https://dl.dropbox.com/u/47239060/Comcast/6121-status-good.PNG <--fast connection
https://dl.dropbox.com/u/47239060/Comcast/6121-signal-good.PNG <--fast connection
https://dl.dropbox.com/u/47239060/Comcast/6121-config-good.PNG <--fast connection

I see quite a few posts about this modem with very similar connection problems. I am assuming the 6120 and 6121 share firmware. The 6120 modem has been performing flawlessly for a couple / three years. I would buy that the 6120 "went bad" as Comcast level 2 suggested to me, but a new modem exhibiting the same problem? Can't be a coincidence...

cheers,

Steve

MaterSnow · ‎08-02-2012

I'm having the same issue with SB6121 as described by others. It just started today. I have no internet connection through this modem since this afternnon. Please let me know if any one found a workaround.

andyross · ‎10-17-2003

I actually have the 6120, but it's basically the same thing and both use the same firmware. No change before or after the firmware update, other than the two new messages in the log after each reboot.

I've been having T4 losses and reboots since July 6. At the moment, I think it's due to the upstream being at about 51dB, and that may be the max when bonded upstream is enabled. Sometimes, it's rebooted and run in a mode where one of the upstream channels (usually the second) has a 'T4 Timeout' message instead of 'Success'.

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Serial Number: blahblahblah
Firmware Build Time: Apr 17 2012 15:09:37

Downstream    Bonding Channel Value
Channel ID    1     5     7     8
Frequency    651000000 Hz    675000000 Hz    687000000 Hz    693000000 Hz
Signal to Noise Ratio    35 dB    35 dB    35 dB    35 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
   2 dBmV     1 dBmV     1 dBmV     1 dBmV

Upstream    Bonding Channel Value
Channel ID    10     11     12
Frequency    36400000 Hz    29500000 Hz    24200000 Hz
Ranging Service ID    4626    4626    4626
Symbol Rate    5.120 Msym/sec    5.120 Msym/sec    2.560 Msym/sec
Power Level    51 dBmV    51 dBmV    50 dBmV
Upstream Modulation    [3] QPSK
[3] 64QAM
    [3] QPSK
[3] 64QAM
    [3] QPSK
[2] 16QAM

Ranging Status    Success    Success    Success

Time    Priority    Code    Message
Aug 02 2012 14:01:40    3-Critical    R02.0    No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 14:01:39    6-Notice    I401.0    TLV-11 - unrecognized OID;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 14:01:39    5-Warning    Z00.0    MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;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=00:22:10:39:d3:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 14:00:57    3-Critical    R04.0    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 13:58:19    3-Critical    R05.0    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 13:58:12    5-Warning    U103.0    Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 13:58:12    5-Warning    U102.0    TCS Partial Service;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 13:58:08    3-Critical    R02.0    No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 13:57:11    6-Notice    I401.0    TLV-11 - unrecognized OID;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 13:57:11    5-Warning    Z00.0    MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;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=00:22:10:39:d3:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 13:56:28    3-Critical    R04.0    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 08:43:02    3-Critical    R05.0    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 08:42:40    5-Warning    U102.0    TCS Partial Service;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 08:42:40    5-Warning    U103.0    Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 08:42:37    3-Critical    R02.0    No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 08:41:39    6-Notice    I401.0    TLV-11 - unrecognized OID;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 08:41:39    5-Warning    Z00.0    MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;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:22:10:39:d3:aa;CMTS-MAC=00:01:5c:31:da:04;CM-QOS=1.1;CM-VER=3.0;

desi99 · ‎08-02-2012

Having the same issue..I am tired of researching and fixing..time to switch to different provider.

Downstream Bonding Channel Value Channel ID 4 2 6 7 Frequency 561000000 Hz 549000000 Hz 573000000 Hz 579000000 Hz Signal to Noise Ratio 35 dB 34 dB 35 dB 36 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 -8 dBmV -10 dBmV -10 dBmV -8 dBmV

Upstream Bonding Channel Value Channel ID 1 Frequency 36000000 Hz Ranging Service ID 931 Symbol Rate 5.120 Msym/sec Power Level 57 dBmV Upstream Modulation [3] QPSK
[3] 64QAM
Ranging Status Success

Signal Stats (Codewords) Bonding Channel ValueChannel ID 4 2 6 7 Total Unerrored Codewords 81681811 81682067 81681896 81681912 Total Correctable Codewords 153 158 150 142 Total Uncorrectable Codewords 1018 746 938 931

Aug 02 2012 20:08:45 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 20:08:45 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;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=94:cc:b9:af:28:19;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 20:04:12 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 20:04:12 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;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=94:cc:b9:af:28:19;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 20:01:56 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 20:01:56 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;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=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;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=94:cc:b9:af:28:19;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:59 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;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=94:cc:b9:af:28:19;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 19:59:34 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;CM-QOS=1.1;CM-VER=3.0; Aug 02 2012 19:59:04 3-Critical R02.0

No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:af:28:19;CMTS-MAC=00:01:5c:31:7d:cc;CM-QOS=1.1;CM-VER=3.0;

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0

Firmware Build Time: Apr 17 2012 15:09:37

sparta1 · ‎01-19-2007

And here as well. I'm 100% convinced it's the new firmware. Sad that action isn't being taken more quickly as there are many "non-technical" people out there probably struggling dealing with tech visits / phone calls when there is nothing they can do to fix it. Comcast needs to step up and address this quickly. Awesome that it happened as I was clicking to post in this thread...

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number:
Firmware Build Time: Apr 17 2012 15:09:37

Power Level47 dBmV 49 dBmV

Aug 02 2012 18:12:49	6-Notice	I401.0	TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 18:12:49	5-Warning	Z00.0	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;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=a4:7a:a4:ef:de:7b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 18:05:33	6-Notice	I401.0	TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 18:05:33	5-Warning	Z00.0	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:25	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;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=a4:7a:a4:ef:de:7b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 17:19:46	6-Notice	I401.0	TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 17:19:46	5-Warning	Z00.0	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;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=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;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=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 17:15:01	6-Notice	I401.0	TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 17:15:01	5-Warning	Z00.0	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:25	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;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=a4:7a:a4:ef:de:7b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 14:59:47	6-Notice	I401.0	TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 14:59:47	5-Warning	Z00.0	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;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=a4:7a:a4:ef:de:7b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 14:24:32	6-Notice	I401.0	TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;
Aug 02 2012 14:24:32	5-Warning	Z00.0	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ef:de:7b;CMTS-MAC=00:21:d8:d2:18:79;CM-QOS=1.1;CM-VER=3.0;

EG · ‎12-24-2003

desi99 wrote:

Having the same issue..I am tired of researching and fixing..time to switch to different provider.

Downstream Bonding Channel Value Channel ID 4 2 6 7 Frequency 561000000 Hz 549000000 Hz 573000000 Hz 579000000 Hz Signal to Noise Ratio 35 dB 34 dB 35 dB 36 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 -8 dBmV -10 dBmV -10 dBmV -8 dBmV

Upstream Bonding Channel Value Channel ID 1 Frequency 36000000 Hz Ranging Service ID 931 Symbol Rate 5.120 Msym/sec Power Level 57 dBmV Upstream Modulation [3] QPSK
[3] 64QAM
Ranging Status Success

FWIW, you have an RF signal / connection quality issue. The upstream power level is out of spec and the downstream is weak. You may also have the other issue but you signals need to addressed first and foremost.

Are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured ?

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then putting them back together again, then perhaps it's best to book a tech visit to investigate and correct.

NB-98087 · ‎03-02-2012

Same issue here.

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number: xxxx
Firmware Build Time: Apr 17 2012 15:09:37

Downstream Bonding Channel Value

Channel ID 33 34 35 36

Frequency 567000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz

Signal to Noise Ratio 36 dB 35 dB 35 dB 35 dB

Downstream Modulation QAM256 QAM256 QAM256 QAM256

Power Level -5 dBmV -6 dBmV -5 dBmV -6 dBmV

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

Upstream Bonding Channel Value

Channel ID 3 1

Frequency 37000000 Hz 30600000 Hz

Ranging Service ID 2458 2458

Symbol Rate 5.120 Msym/sec 5.120 Msym/sec

Power Level 54 dBmV 54 dBmV

Upstream Modulation [3] QPSK [3] 64QAM [3] QPSK [3] 64QAM

Ranging Status Success Success

Signal Stats (Codewords) Bonding Channel Value

Channel ID 33 34 35 36

Total Unerrored Codewords 39906591 39001783 39001888 39001850

Total Correctable Codewords 50 30 103 318

Total Uncorrectable Codewords 676 584 553 531

Error Logs:

Aug 02 2012 18:57:58

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 18:57:58

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;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=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 17:51:37

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 14:31:11

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 14:31:11

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;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=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 11:01:51

3-Critical

R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 31 2012 05:43:25

4-Error

D103.0

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 28 2012 13:31:09

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 28 2012 13:31:09

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;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=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 28 2012 13:11:33

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 26 2012 21:55:44

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 26 2012 21:55:44

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;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=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Jul 26 2012 14:58:30

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 24 2012 23:18:11

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;CM-QOS=1.1;CM-VER=3.0;

Jul 24 2012 23:18:11

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:1d:70:cc:54:3c;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=a4:7a:a4:ee:f2:ce;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Paul858 · ‎08-02-2012

Is there likely to be an official Comcast response to this? I have a tech coming over tomorrow and I could save them a trip if this is indeed a firmware issue with this modem?

Anyone know?

EG · ‎12-24-2003

NB-98087 wrote:

Same issue here.

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number: xxxx
Firmware Build Time: Apr 17 2012 15:09:37

Downstream                                          Bonding Channel Value

Channel ID                                    33                      34                    35                         36

Frequency                          567000000 Hz     573000000 Hz    579000000 Hz     585000000 Hz

Signal to Noise Ratio               36 dB                   35 dB                  35 dB                 35 dB

Downstream Modulation        QAM256              QAM256             QAM256            QAM256

Power Level                           -5 dBmV              -6 dBmV              -5 dBmV            -6 dBmV

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

Upstream                                                    Bonding Channel Value

Channel ID                                         3                             1

Frequency                                37000000 Hz             30600000 Hz

Ranging Service ID                         2458                         2458

Symbol Rate                            5.120 Msym/sec     5.120 Msym/sec

Power Level                               54 dBmV                     54 dBmV

Upstream Modulation     [3] QPSK [3] 64QAM     [3] QPSK [3] 64QAM

Ranging Status                        Success                        Success

Signal Stats (Codewords)                              Bonding Channel Value

Channel ID                                       33                     34                      35                         36

Total Unerrored Codewords       39906591        39001783          39001888             39001850

Total Correctable Codewords          50                     30                     103                       318

Total Uncorrectable Codewords     676                   584                    553                       531

You too. The upstream power is out of spec and the downstream is a bit weak. Same drill as above.

djlandkpl1 · ‎09-23-2008

I have been having T3/T4 errors every 2 to 4 hours in the last few days. I had a tech at the house who found no ingress and the levels to be acceptable. As soon as he left, I had 3 reboots in 3 hours. Today (8/3) seems better. It seems on each reboot the upstream channel changes. I'm about to reconnect my old DOCSIS 2 modem so I have a reliable connection.

Downstream

Bonding Channel Value

Channel ID

105

106

107

108

Frequency

681000000 Hz

687000000 Hz

693000000 Hz

699000000 Hz

Signal to Noise Ratio

37 dB

36 dB

37 dB

Downstream Modulation

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

-4 dBmV

Upstream

Bonding Channel Value

Channel ID

2

Frequency

36500000 Hz

Ranging Service ID

2592

Symbol Rate

5.120 Msym/sec

Power Level

45 dBmV

Upstream Modulation

[3] QPSK
[3] 64QAM

Ranging Status

Success

Signal Stats (Codewords)

Bonding Channel Value

Channel ID

105

106

107

108

Total Unerrored Codewords

1496109218

1495285606

1495285009

1495288202

Total Correctable Codewords

2193

3043

2967

2710

Total Uncorrectable Codewords

8916

11768

12615

9811

Cable Modem

Status

Signal

Addresses

Configuration

Logs

Open Source

Help

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

Time

Priority

Code

Message

Aug 03 2012 00:43:20

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 00:43:20

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;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=a4:7a:a4;CMTS-MAC=00:13:5f:00:b2:00;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=a4:7a:;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 00:42:24

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 22:57:52

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=a4:7a:;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:29:38

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a:;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:29:38

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:20

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:18

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;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=a4:7;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:28:31

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:28:01

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=a4:7a:;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:27:52

4-Error

C401.0

DCC-ACK not received;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:27:52

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=a4:7;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:04:36

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:04:36

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:20

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;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=a4:7a:a4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Aug 02 2012 20:03:29

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:7a;CMTS-MAC=00:13:5f:00:b2:00;CM-QOS=1.1;CM-VER=3.0;

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Firmware Build Time: Apr 17 2012 15:09:37

bharper32 · ‎08-01-2012

I also am having a problem with the SB6121 Modem. I had a tech out today, and he confirmed that everything in the line is fine, that comcast must have made a change either in my modem firmware, or something in the head end that is effecting the handshake. He said that a firmware upgrade to the SB6121 may fix the problem, but to definately inform comcast that it is probably something that they have changed, because of the way all the users seem to have the same time-line to the problem.

I only have one upload chanel, but he assures me that the other chanels are there, and working fine according to his instruments.

Here are my Stats:

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number: xxxxxxxxxxxxxxxxxxxxxxxxxx
Firmware Build Time: Apr 17 2012 15:09:37

Downstream

Bonding Channel Value

Channel ID

65

66

67

68

Frequency

579000000 Hz

585000000 Hz

591000000 Hz

597000000 Hz

Signal to Noise Ratio

37 dB

36 dB

37 dB

Downstream Modulation

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

0 dBmV

Upstream

Bonding Channel Value

Channel ID

1

Frequency

34800000 Hz

Ranging Service ID

114

Symbol Rate

5.120 Msym/sec

Power Level

48 dBmV

Upstream Modulation

[3] QPSK
[3] 64QAM

Ranging Status

Success

Signal Stats (Codewords)

Bonding Channel Value

Channel ID

65

66

67

68

Total Unerrored Codewords

258546674

257783045

257783134

257783319

Total Correctable Codewords

23

9

10

2

Total Uncorrectable Codewords

673

546

601

568

Time

Priority

Code

Message

Aug 03 2012 11:21:05

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=74:f6:12:67:c0:b0;CMTS-MAC=c4:71:fe:76:94:68;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 11:21:05

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=74:f6:12:67:c0:b0;CMTS-MAC=c4:71:fe:76:94:68;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=74:f6:12:67:c0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 11:14:43

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:f6:12:67:c0:b0;CMTS-MAC=c4:71:fe:76:94:68;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 11:14:31

3-Critical

T05.0

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=74:f6:12:67:c0:b0;CMTS-MAC=c4:71:fe:76:94:68;CM-QOS=1.1;CM-VER=3.0;

Aug 01 2012 12:10:11

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=74:f6:12:67:c0:b0;CMTS-MAC=c4:71:fe:76:94:68;CM-QOS=1.1;CM-VER=3.0;

Aug 01 2012 12:10:11

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=74:f6:12:67:c0:b0;CMTS-MAC=c4:71:fe:76:94:68;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=74:f6:12:67:c0:b0;CMTS-MAC=c4:71:fe:76:94:68;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:13

6-Notice

N/A

Cable Modem Reboot from GUI/Configuration page ;CM-MAC=74:f6:12:67:c0:b0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

bobcali · ‎08-02-2012

So I did find a work around for my configuration that helped things a bunch.

The SB6121 config page says its in iPv4 only mode. I'm running my SB6121 connected to an Apple Airport Extreme Base Station Gen 5 wireless router. The internet connection settings on the AEBS were set to configure iPv6 'automatically via tunnel'. I've done a bunch of testing and if the AEBS is set to use iPv6 with any setting other than 'link-local only' (such as automatic via native or tunnel, etc.) the instability returns within a few minutes.

While I'm still getting the same error messages I was before, I have been able to get a much more consistent connection at the same 25/4 mb/s up and down I was getting before by making this router configuration change.

The exact steps I used:

-open airport utility and click on your AEBS

-select 'edit'

-click on 'internet' tab (if you see any addresses listed under iPv6 DNS Servers that is likely the problem)

-select 'internet options'

-make sure the configure iPv6 drop down is 'link-local only'

-click save and then update

-after it completes the update unplug the AEBS

-ideally, also power down all of the devices you have connected to the AEBS (to flush their DNS caches)

-in your web browser bring up the SB6121 configuration page at 192.168.100.1

-click on configuration page and select reset all defaults and say OK to the warning about time to restore

-click on restart cable modem

-after the cable modem is operational again with all 4 indicator lights solidly lit unplug the SB6121

-power on the SB6121 until all 4 indicator lights are solidly lit

-power on the AEBS

-power on and reconnect your devices to the network

It seems to have solved the problem for me so at least I'm not disconnecting multiple times every few minutes. I've been running for 24 hours with no problems now. If I change the iPv6 settings to something else I'm go right back to the prior situation so it doesn't seem like this was a Comcast change that improved the situation.

EG · ‎12-24-2003

bobcali wrote:

The SB6121 config page says its in iPv4 only mode.

Everything else aside, that really means nothing to the end user or to the LAN side of the modem. It only concerns the DOCSIS (WAN) side and whether or not the modem is getting a private (in house) managerial IP address which the provder uses to manage / contact / update it. The modem is a bridge and it will pass a public IP address (IPv4 or 6) on to the device that is directly connected to it.

bobcali · ‎08-02-2012

Since I was able to connect using ipv6 to ipv6-test.com and test-ipv6.com and pass all of the ipv4 AND ipv6 connection tests when the AEBS router was configured in ipv6 mode to automatically connect via native or tunnel I figured the SB6121 must be capable of passing both and it was possibly a router related problem.

But the main question remains: is the root cause here that home routers configured to use ipv6 are now having connectivity problems because of a change made to Comcast's network config recently or is it really a SB6121 firmware upgrade bug? My testing seems to show that I can operate the SB6121 fine as long as the router does not try to connect using ipv6 and it is in ipv4 only mode...and that seems like it would be caused by something changing with Comcast's network (like adding ipv6 DNS servers in DHCP mode) since I didn't change this rather esoteric and buried ipv6 setting in my AEBS when this problem started.

Would be great if someone who knows what changed at Comcast could answer this question and save everyone a bunch of time.

sashanj · ‎06-23-2012

Channel ID

1

3

5

6

Frequency

705000000 Hz

717000000 Hz

729000000 Hz

735000000 Hz

Signal to Noise Ratio

35 dB

31 dB

Downstream Modulation

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

0 dBmV

1 dBmV

0 dBmV

Upstream Bonding Channel Value

Channel ID	10	11	12
Frequency	36200000 Hz	29400000 Hz	22000000 Hz
Ranging Service ID	7806	7806	7806
Symbol Rate	5.120 Msym/sec	5.120 Msym/sec	2.560 Msym/sec
Power Level	51 dBmV	50 dBmV	51 dBmV
Upstream Modulation	[3] QPSK [3] 64QAM	[3] QPSK [3] 64QAM	[3] QPSK [2] 16QAM
Ranging Status	Success	T4 TimeOut	Success

Signal Stats (Codewords) Bonding Channel Value

Channel ID	1	3	5	6
Total Unerrored Codewords	3405778917	3405145347	3405145442	399605805
Total Correctable Codewords	15	6	1	1530078840
Total Uncorrectable Codewords	695	758	628	1477593161

Aug 03 2012 17:40:28

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:39:13:21;CMTS-MAC=00:01:5c:22:c3:90;CM-QOS=1.1;CM-VER=3.0;

MDD Recovery following MDD Loss;CM-MAC=cc:7d:37:39:13:21;CMTS-MAC=00:01:5c:22:c3:90;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 17:36:23

5-Warning

T202.0

Lost MDD Timeout;CM-MAC=cc:7d:37:39:13:21;CMTS-MAC=00:01:5c:22:c3:90;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 17:36:23

5-Warning

N/A

DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=cc:7d:37:39:13:21;CMTS-MAC=00:01:5c:22:c3:90;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 17:35:58

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:7d:37:39:13:21;CMTS-MAC=00:01:5c:22:c3:90;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 17:35:38

6-Notice

N/A

MDD Recovery following MDD Loss;CM-MAC=cc:7d:37:39:13:21;CMTS-MAC=00:01:5c:22:c3:90;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 17:35:36

5-Warning

T202.0

Lost MDD Timeout;CM-MAC=cc:7d:37:39:13:21;CMTS-MAC=00:01:5c:22:c3:90;CM-QOS=1.1;CM-VER=3.0;

etc.

By The way, Status page always says:

Cable Modem Status Offline

wgrecap · ‎08-02-2012

Original Thread:

http://forums.comcast.com/t5/Connectivity-and-Modem-Help/motorola-SB6121-drops-and-is-getting-worse/...

Added a second set of working logs

Not Working

http://dl.dropbox.com/u/221803/Comcast/Not%20Worki?ng/not%20working%20Logs.PNG

http://dl.dropbox.com/u/221803/Comcast/Not%20Worki?ng/not%20working%20Signal.PNG

http://dl.dropbox.com/u/221803/Comcast/Not%20Worki?ng/not%20working%20Status.PNG

Working

http://dl.dropbox.com/u/221803/Comcast/Working/wor?king%20Logs.PNG

http://dl.dropbox.com/u/221803/Comcast/Working/wor?king%20Signal.PNG

http://dl.dropbox.com/u/221803/Comcast/Working/wor?king%20Status.PNG

Not Working Again

http://dl.dropbox.com/u/221803/Comcast/Not%20Worki?ng%202/not%20working%202%20Signal.PNG

Working Again

http://dl.dropbox.com/u/221803/Comcast/Working%202/working2%20Help.png

http://dl.dropbox.com/u/221803/Comcast/Working%202/working2%20logs.PNG

http://dl.dropbox.com/u/221803/Comcast/Working%202/working2%20signal.PNG

MaterSnow · ‎08-02-2012

I had issues with splitters going bad. Comcast tech replaced the splitters and then it started working again.

fourtwizzy · ‎08-04-2012

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number: 359079207720116701012019
Firmware Build Time: Apr 17 2012 15:09:37

Aug 03 2012 16:37:41 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;CM-QOS=1.1;CM-VER=3.0; Aug 03 2012 16:37:41 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:25 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;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=a4:7a:a4:6d:78:fe;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 03 2012 16:36:25 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;CM-QOS=1.1;CM-VER=3.0; Aug 03 2012 16:35:55 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;CM-QOS=1.1;CM-VER=3.0; Aug 03 2012 16:35:46 4-Error C401.0 DCC-ACK not received;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;CM-QOS=1.1;CM-VER=3.0;

Aug 03 2012 16:35:46

Channel ID 113 114 115 116 Frequency 711000000 Hz 717000000 Hz 723000000 Hz 729000000 Hz Signal to Noise Ratio 37 dB 38 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 11 dBmV 11 dBmV 10 dBmV 10 dBmV 3-Critical R02.0

No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:6d:78:fe;CMTS-MAC=00:1d:70:af:cd:79;CM-QOS=1.1;CM-VER=3.0;

fourtwizzy · ‎08-04-2012

Questions

1) what are the odds comcast resolves this soon?

2) what is a better modem to purchase I don't feel like waiting on comcast to get their act together

EG · ‎12-24-2003

fourtwizzy wrote:

2) what is a better modem to purchase I don't feel like waiting on comcast to get their act together

May I recommend a Zoom 5341J (note the "J") model. A very good and future proof purchase due to the DOCSIS 3 8x4 multiple channel bonding compared to the 6120 & 6121 being only 4x4 capable. I am using one as we speak and it's been a bulletproof performer !

andyross · ‎10-17-2003

By The way, Status page always says:
Cable Modem Status Offline

The 'offline' status is because one of your upstream channels has a Ranging status of 'T4 Timeout'. That's because it's at or near the maximum transmit level of 51dBmV. It's the same issue I'm suffering through.

fourtwizzy · ‎08-04-2012

has any fixed their issue by just replacing their modem. I live in an apartment building and I am unsure if the lines / splitters are causing the issue or if more than likely the modem is the issue. I'd like to get a technician out here but comcast wants to tell me it's my modem / router since I do not rent equipment from them. What are the odds I can fix the issue by just purchasing a new modem?

johnthehammer23 · ‎08-04-2012

Lines were just balanced a few months ago and my signal levels still look fine. Connection issues just started today.

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Serial Number: ######
Firmware Build Time: Apr 17 2012 15:09:37

Aug 04 2012 12:17:57 3-Critical R02.0 No Ranging Response received - T3 time-out;
CM-MAC=##:##:##:##:##:##;
CMTS-MAC=00:01:5c:22:ae:cd;
CM-QOS=1.1;
CM-VER=3.0;
Aug 04 2012 12:13:04 6-Notice I401.0 TLV-11 - unrecognized OID;
CM-MAC=##:##:##:##:##:##;
CMTS-MAC=00:01:5c:22:ae:cd;
CM-QOS=1.1;
CM-VER=3.0;
Aug 04 2012 12:13:04 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;
CM-MAC=##:##:##:##:##:##;
CMTS-MAC=00:01:5c:22:ae:cd;
CM-QOS=1.1;
CM-VER=3.0;
Jan 01 1970 00:01:26 3-Critical R02.0 No Ranging Response received - T3 time-out;
CM-MAC=##:##:##:##:##:##;
CMTS-MAC=00:01:5c:22:ae:cd;
CM-QOS=1.1;
CM-VER=3.0;
Jan 01 1970 00:01:14 3-Critical D01.0 DHCP FAILED - Discover sent, no offer received;
CM-MAC=##:##:##:##:##:##;
CMTS-MAC=00:01:5c:22:ae:cd;
CM-QOS=1.1;
CM-VER=3.0;
Jan 01 1970 00:00:39 3-Critical R02.0 No Ranging Response received - T3 time-out;
CM-MAC=##:##:##:##:##:##;
CMTS-MAC=00:01:5c:22:ae:cd;
CM-QOS=1.1;
CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;
CM-MAC=##:##:##:##:##:##;
CMTS-MAC=00:00:00:00:00:00;
CM-QOS=1.1;
CM-VER=3.0;

Channel ID 3 4 5 6

Frequency 681000000 Hz 687000000 Hz 693000000 Hz 699000000 Hz

Signal to Noise Ratio 37 dB 38 dB 38 dB 38 dB

Downstream Modulation QAM256 QAM256 QAM256 QAM256

Power Level 13 dBmV 13 dBmV 13 dBmV 13 dBmV

Upstream Bonding Channel ValueChannel ID 1 2 Frequency 36400000 Hz 29500000 Hz Ranging Service ID 2924 2924 Symbol Rate 5.120 Msym/sec 2.560 Msym/sec Power Level 45 dBmV 44 dBmV Upstream Modulation[3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
Ranging Status Success Success

Signal Stats (Codewords) Bonding Ch

Channel ID 3 4 5 6

Total Unerrored Codewords 32942236 32283009 32283011 32283276

Total Correctable Codewords 17 0 0 0

Total Uncorrectable Codewords 2921 1310 1437 1300

PlaneWryter · ‎08-02-2012

Been doing way more debugging on this Comcast-connectivity issue than a customer should.

First, to calibrate, here’s a screenshot of my SB6121’s Help page showing model, Firmware, etc.:

Now, here’s some findings collected over the last ~36 hours which might be helpful to others.

FINDING ONE: REPEATING PATTERN in ERROR LOGS

While it seems that the SB6121 logging function captures very few events, the following pattern has been more-or-less repeated frequently:

3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0;
3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0;
3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0;
6-Notice	I401.0	TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0;
5-Warning	Z00.0	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=94:cc:b9:18:f0:a9;CMTS-MAC=c4:71:fe:76:1d:40;CM-QOS=1.1;CM-VER=3.0;

Can anyone interpret the meaning of R07.0 and R02.0 Error Codes?

FINDING TWO: MANY UPSTREAM BONDING PROBLEMS

A few times when Internet connectivity fails, I was able to record the “Signal” page with SnagIt.

Follows are four interesting screenshots; notice the “Aborted Ranging Status” for Upstream Bonding Channels and the Power Level (i.e., 0 dBmV):

Channel ID 1 Failed

Channel ID 3 Failed

Channel ID 1 & 3 Failed

Channel ID 2 & 3 Failed

FINDING THREE: IMPAIRED ACCESS TO SB6121 CONSOLE

Many times—yet not always—when the internet is down, the SB6121’s console (192.168.100.1) is unavailable from Safari or Chrome. The response seems to be a 404-like error.

Please see Finding Four (below) for important comment.

FINDING FOUR: ETHERNET INDICATOR FREEZES

Three times I’ve noticed that—when the Internet is down—the SB6121 seems to enter an indeterminate state where the Ethernet signal indicator freezes into a solid blue (i.e., it does not flash).

NOTE: With respect to Finding Three (above), whenever the SB6121’s Ethernet indicator freezes, its Console is always unreachable. However, the reverse is not true. The Console can be unreachable, yet the Ethernet indicator is flashing.

Do you experience similar symptoms? Any ideas? What do you think is the best thing to do next? Is there enough information here to persuade Comcast to dispatch skilled techs to our residences?

Your suggestions are welcomed; thanks!

andyross · ‎10-17-2003

Tech was just here. Good news is he was a real tech and knew a few things and understood what I was talking about. The bad news is he couldn't do much. His equipment showed about 43dB at the post, and 46 at where it comes into my apartment. About right for that distance. Add in 3-4 for the splitter, and you get the 50 or so I see. He did replace one connector. The initial connection looked good, showing about 48/49/48, but it's crept up a bit since.

He said they are aware of these issues, and have been emphasizing trying to improve upstream issues. I gave him a printout of the CableLabs table showing the maximum signal levels from that specs link given in another post.

At worst, for now, if I run into major issues, I can put in a 6dB tap in place of the splitter. That would gain about 1dB to the modem, at the expense of the TV. Hopefully, not enough to affect it.

Hopefully, Comcast will see all these issues and maybe either:
Stop upstream bonding for now until they can get the infrastructure improved.
Somehow limit the upstream bonding to two channels, which would allow up to 54dB and give a little more headroom.

Update: the middle channel has T4'd out, even though signals are 50/49/50. Very weird.

mcollins757 · ‎08-04-2012

Same problems here. Intermittant disconnect and very slow speeds.

cmhelp-good

cmlogs-good

cmsignal-good

andyross · ‎10-17-2003

mcollins757 wrote:
Same problems here. Intermittant disconnect and very slow speeds.
cmhelp-good
cmlogs-good
cmsignal-good

I only see reboots due to SNMP (not sure what that means) or power resets. The TLV and MIMO things appear to be nuisance messages added since the firmware upate.

drq2 · ‎08-05-2012

I just started having the same issue here. Rebooting the Modem from the GUI seems to resolve the issue.

If this is a firmware problem then you should roll back the firmware until you get this fixed. I don't pay this much per month to do beta testing for you.

Here is the info after a reboot when working and followed by the signal and logs after connection loss.

SIGNALS:

Downstream Bonding Channel Value Channel ID 2 3 7 8 Frequency 621000000 Hz 627000000 Hz 651000000 Hz 657000000 Hz Signal to Noise Ratio 36 dB 36 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 -5 dBmV -5 dBmV

Upstream Bonding Channel Value Channel ID 4 5 6 Frequency 36500000 Hz 29800000 Hz 23800000 Hz Ranging Service ID 2555 2555 2555 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level 51 dBmV 51 dBmV 52 dBmV Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
Ranging Status Success Success Success

Signal Stats (Codewords) Bonding Channel ValueChannel ID 2 3 7 8 Total Unerrored Codewords 17512688 11545411 11544724 11548235 Total Correctable Codewords 810 863 1313 510 Total Uncorrectable Codewords 10645 8307 8704 6099

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Firmware Build Time: Apr 17 2012 15:09:37

ERROR

Time Priority Code Message Aug 05 2012 08:36:43 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:30:13 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:30:01 5-Warning U102.0 TCS Partial Service;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:30:01 5-Warning U103.0 Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:29:53 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:29:00 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:29:00 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:27:00 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:59 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:59 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:57 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:37 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:59:05 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:59:05 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:57:58 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:53:28 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:53:22 5-Warning U103.0 Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:53:22 5-Warning U102.0 TCS Partial Service;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0;

Here is the ERROR STATE:

Downstream Bonding Channel Value Channel ID 3 4 5 7 Frequency 627000000 Hz 633000000 Hz 639000000 Hz 651000000 Hz Signal to Noise Ratio 36 dB 36 dB 36 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 -5 dBmV -5 dBmV

Upstream Bonding Channel Value Channel ID 4 5 6 Frequency 36500000 Hz 29800000 Hz 23800000 Hz Ranging Service ID 666 666 666 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level 51 dBmV 46 dBmV 52 dBmV Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
Ranging Status Success T4 TimeOut Success

Signal Stats (Codewords) Bonding Channel Value Channel ID 3 4 5 7 Total Unerrored Codewords 32027132 32027134 32027256 32027258 Total Correctable Codewords 13 19 0 0 Total Uncorrectable Codewords 1607 1600 1430 1430

LOGS

Time Priority Code Message Aug 05 2012 08:41:43 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:30:13 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:30:01 5-Warning U102.0 TCS Partial Service;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:30:01 5-Warning U103.0 Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:29:53 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:29:00 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:29:00 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:27:00 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:59 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:59 5-Warning T202.0 Lost MDD Timeout;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:57 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 08:26:37 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:59:05 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:59:05 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:57:58 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:53:28 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:53:22 5-Warning U103.0 Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0; Aug 05 2012 07:53:22 5-Warning U102.0 TCS Partial Service;CM-MAC=00:22:10:39:f4:d8;CMTS-MAC=00:01:5c:23:0c:11;CM-QOS=1.1;CM-VER=3.0;

D-Smoke · ‎08-05-2012

I am also having disconnect issues figured I would add to the posts to hopefully have something get done about it. I didn't have any trouble with it before the firmware upgrade but this could be just coincidence. A few hours ago my modem was being extremely slow pages would barley load. Did a ping test google.com was timing out. I power cycled the modem and it would try and sync up but keep looping trying to boot. I just left it alone did something else came back a few hours later and it was fine. I did do a reset to all defaults before I left it. I found this thread by searching unrecognized OID which I see in the log file. My signal levels are good so not sure if this is a bug or what. It's only happened a few times where I couldn't get on and it's stuck in a boot loop. It will eventually fix come back if I let it sit. I'm really disappointed I had a 6120 since it first came out before you could even buy them at retail I had it leased. Never had any issues with it wouldn't reset it for months at a time. I have only had this modem a month and already issues. I recommended this modem to a friend as well since it was rated the high 3 stars for Comcast certification. I hope this get fixed soon if Comcast wants my log files please contact me will gladly provide logs. Here is my signal levels levels they look good. I'm not going doing anything right now since it seems to be a big problem and it doesn't happen enough for me to go get another mode. When this modem does work it works great and the random disconnects haven't been that often but still annoying.

I have no splitters or cable boxes. Line from outside into coupler into 1 line to where the modem is direct connection to modem.

http://img14.imageshack.us/img14/2819/logf.png

Aug 05 2012 05:52:20    6-Notice    I401.0    TLV-11 - unrecognized OID;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Aug 05 2012 05:52:20    5-Warning    Z00.0    MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:14:31    3-Critical    D01.0    DHCP FAILED - Discover sent, no offer received;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:12:28    3-Critical    R02.0    No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

This looks like a pretty big problem, would be nice to hear from comcast in this thread to aknowledge this is an issue and keep us posted on updates. This is suppose to be the best Docsis 3 modem. I hope this gets fixed soon.

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Firmware Build Time: Apr 17 2012 15:09:37

mcollins757 · ‎08-04-2012

Thanks for the reply Andy. Any clues as to if Comcast is working on this issue? Do you think a roll back would be terribly difficult for them?

EG · ‎12-24-2003

andyross wrote:
I only see reboots due to SNMP (not sure what that means) or power resets.

I believe that these particular log entries mean that the are deliberately doing it from their end via the SNMP management protocol. Seems that someone has been polling the modem for the purpose of re-booting it.

djlandkpl1 · ‎09-23-2008

I was working my issues via another forum. ComcastSteve reprovisioned my modem on Friday at Noon. Since then I've had 1 T4 reboot and I am not seeing T3 errors like I was. I don't know if anything was changed during the provisioning process but so far so good.

itisdesign · ‎08-02-2012

My SB6120 and SB6121 both experience random connectivity drops. Since my reply is quite lengthy, I've created a new thread (which contains the requested information) here: http://forums.comcast.com/t5/Connectivity-and-Modem-Help/SB6120-and-SB6121-connectivity-temp-restore...

Btw, thanks very much for starting this thread!

SteveLiebler · ‎08-02-2012

Same old S(tuff): It seemed to settle down over the weekend.

Cheers,

Steve

TexasBigDawg · ‎08-06-2012

Same thing as everyone else...... I have spent several hours on the phone with Comcast and the issue is no better. The problems usually quits between 1-2 pm CST???? They are sending a tech out this week.

Someone mentioned the Zoom 5341J modem - is that any better than the SB6121???? Or are we vulnerable to the same issue....

TexasBigDawg · ‎08-06-2012

never mind... After looking on the Comcast site I found the exact same problem started at the exact same time with that modem too...

http://forums.comcast.com/t5/Connectivity-and-Modem-Help/Zoom-5341J-Firmware-upgrade/td-p/1366941

justinnigro · ‎08-06-2012

Issues here starting last week. Here are my logs:

Downstream Bonding Channel Value Channel ID 2 1 3 7 Frequency 723000000 Hz 717000000 Hz 729000000 Hz 753000000 Hz Signal to Noise Ratio 28 dB 26 dB 31 dB 36 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 1 dBmV 1 dBmV 1 dBmV -1 dBmV

Upstream Bonding Channel Value Channel ID 11 10 12 Frequency 30600000 Hz 25300000 Hz 37000000 Hz Ranging Service ID 5923 5923 5923 Symbol Rate 5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec Power Level 40 dBmV 39 dBmV 40 dBmV Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM
[3] QPSK
[3] 64QAM
Ranging Status Success Success Success

Signal Stats (Codewords) Bonding Channel Value Channel ID 2 1 3 7 Total Unerrored Codewords 48474233 4675410 48612906 48612995 Total Correctable Codewords 138682 26339625 11 43 Total Uncorrectable Codewords 751 17383437 753 629

Aug 06 2012 07:02:11 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:02:11 5-Warning T202.0 Lost MDD Timeout;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:02:11 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:01:35 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:01:26 5-Warning T202.0 Lost MDD Timeout;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:01:26 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:00:45 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:00:34 5-Warning T202.0 Lost MDD Timeout;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 07:00:34 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:59:54 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:59:51 5-Warning T202.0 Lost MDD Timeout;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:59:51 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:59:26 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:58:42 5-Warning T202.0 Lost MDD Timeout;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:58:42 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:58:14 6-Notice N/A MDD Recovery following MDD Loss;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:54:36 5-Warning T202.0 Lost MDD Timeout;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:54:36 5-Warning N/A DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0; Aug 06 2012 06:54:07 5-Warning T07.0 RCS Partial Service;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 06:54:06

6-Notice I401.0

TLV-11 - unrecognized OID;CM-MAC=94:cc:b9:18:78:30;CMTS-MAC=00:01:5c:33:0e:0c;CM-QOS=1.1;CM-VER=3.0;

DirtyRed1225 · ‎08-06-2012

Same issues as the rest but I have a SB6120, I think using the same firmware as SB6121.

Here are my specs.

Channel ID 2 3 5 7

Frequency 693000000 Hz 699000000 Hz 711000000 Hz 723000000 Hz

Signal to Noise Ratio 37 dB 38 dB 38 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

0 dBmV 0 dBmV 0 dBmV 0 dBmV

Channel ID 11 12

Frequency 36400000 Hz 29500000 Hz

Ranging Service ID 562 562

Symbol Rate 5.120 Msym/sec 2.560 Msym/sec

Power Level 54 dBmV 54 dBmV

Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM

Ranging Status Success Success

Signal Stats (Codewords) Bonding Channel Value

Channel ID 2 3 5 7

Total Unerrored Codewords 262692129 261016436 261016526 261016352

Total Correctable Codewords 0 1 0 0

Total Uncorrectable Codewords 1361 1408 1456 1425

My error logs

Time

Priority

Code

Message

Aug 06 2012 08:16:23

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:16:23

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:36

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;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=e4:83:99:8b:6d:8e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:15:18

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:14:48

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:14:46

3-Critical

R06.0

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:14:46

3-Critical

R03.0

Ranging Request Retries exhausted;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:14:46

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:49

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:49

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;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=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:06

3-Critical

R06.0

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:06

3-Critical

R03.0

Ranging Request Retries exhausted;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:05

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:05

3-Critical

R06.0

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:05

3-Critical

R03.0

Ranging Request Retries exhausted;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 08:01:04

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 07:18:44

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Aug 06 2012 07:18:44

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e4:83:99:8b:6d:8e;CMTS-MAC=00:01:5c:23:00:02;CM-QOS=1.1;CM-VER=3.0;

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Serial Number: 317001113300491808040011
Firmware Build Time: Apr 17 2012 15:09:37

EG · ‎12-24-2003

TexasBigDawg wrote:

never mind... After looking on the Comcast site I found the exact same problem started at the exact same time with that modem too...

http://forums.comcast.com/t5/Connectivity-and-Modem-Help/Zoom-5341J-Firmware-upgrade/td-p/1366941

That's just an issue with the access to the user interface and not a connectivity issue. I have no connectivity issues with my 5341J with the new firmware load. Also the 5341J is 8x4 multiple bonded channel capable whereas the 6121 is only 4x4 capable.

EG · ‎12-24-2003

DirtyRed1225 wrote:

Same issues as the rest but I have a SB6120,

Please see the response in your thread here;

http://forums.comcast.com/t5/Connectivity-and-Modem-Help/SB6120-keeps-rebooting/m-p/1369261

andyross · ‎10-17-2003

Since the tech came out Saturday, and a reboot after some rains and cooler weather, it's been stable. Signal is still about 48-49.

I noticed another post where the middle upstream channel was showing T4 timeout in the ranging status, even though signal levels looked good. For those who see that 'offline' modem home page, is it also the middle channel showing the timeout? Look at the frequencies to see if it's in the middle, as they may not be bonded in order.

I wonder if the transmitter in the modem isn't keeping the channels well separated, and out-of-band noise from the outer two could be causing problems with the middle channel.

EG · ‎12-24-2003

andyross wrote:
I wonder if the transmitter in the modem isn't keeping the channels well separated,

FWIW, I believe that the modem's "transmitter" does what ever it is told to do by the CMTS's instructions.

Puh · ‎08-07-2012

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number:
Firmware Build Time: Apr 17 2012 15:09:37

Downstream
Channel ID     73     74     75     76
Frequency     543000000 Hz     549000000 Hz     555000000 Hz     561000000 Hz
Signal to Noise Ratio     36 dB     35 dB     36 dB     36 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
    3 dBmV     4 dBmV     4 dBmV     4 dBmV

Upstream
Channel ID     3     4
Frequency     32400000 Hz     22800000 Hz
Ranging Service ID     7118     7118
Symbol Rate     5.120 Msym/sec     5.120 Msym/sec
Power Level     32 dBmV     32 dBmV
Upstream Modulation     [3] QPSK   [3] QPSK

                                               [3] 64QAM   [3] 64QAM
Ranging Status     Success     Success

Signal Stats (Codewords)     Bonding Channel Value
Channel ID     73     74     75     76
Total Unerrored Codewords     195730022     195008801     195008835     195008467
Total Correctable Codewords     127     366     510     968
Total Uncorrectable Codewords     550     559     526     583

Logs
Aug 07 2012 00:16:38     6-Notice     I401.0     TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Aug 07 2012 00:16:38     5-Warning     Z00.0     MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;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=a4:7a:a4:77:ca:ba;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 23:57:08     6-Notice     I401.0     TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 23:57:08     5-Warning     Z00.0     MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;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=a4:7a:a4:77:ca:ba;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 23:55:10     6-Notice     I401.0     TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 23:55:10     5-Warning     Z00.0     MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:33     5-Warning     D04.1     ToD request sent - No Response received;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:25     3-Critical     R02.0     No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;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=a4:7a:a4:77:ca:ba;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 23:52:39     6-Notice     I401.0     TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 23:52:39     5-Warning     Z00.0     MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:33     5-Warning     D04.1     ToD request sent - No Response received;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:20     3-Critical     R02.0     No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:06     3-Critical     D01.0     DHCP FAILED - Discover sent, no offer received;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:57     3-Critical     R02.0     No Ranging Response received - T3 time-out;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;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=a4:7a:a4:77:ca:ba;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 21:51:33     4-Error     D103.0     DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;
Aug 06 2012 18:53:26     6-Notice     I401.0     TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:77:ca:ba;CMTS-MAC=00:1d:70:af:c4:74;CM-QOS=1.1;CM-VER=3.0;

Just had a Tech come out 2 weeks ago to replace the cables in the attic to get signal levels to normal, about 3 days ago we started having random disconnects and horrible lag after resetting the modem. I've tried resetting the modem 500 times. Honestly i'm at a loss as to what to do next...
Should i call another tech out, Reset the modem to factory defaults, Or wait for a comcast to fix it themself.. I just bought the modem a month ago, I'd really rather not buy another one, since it's still under warrenty (plus i got the extended warrenty from newegg) and i just rid myself the 7 dollar modem rental fee...

Edit: removed serial number...

swimfin69 · ‎08-07-2012

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 5.0
Serial Number: 359058114703319301012019
Firmware Build Time: Apr 17 2012 15:09:37

Logs show T3 and T4 errors.

trent5 · ‎08-07-2012

Last night my SB6121 received the new firmware update. At the same time, whether related or not, I lost upstream channel bonding (used to be 4x3, now 4x1) and my upstream power level gained 10dBmV (from 47-49 to a steady 57dBmV). Connection has been stable since this happened 12 hours or so ago, but cannot be sure on the long run with such upstream power levels. Although my upload speed has dropped a bit with the loss of upstream channel bonding. Have Blast with the new double speeds already active.

I tried numerous times to reset to defaults, unplug power, wait for a few minutes, and reconnect. Same outcome.

No splitters installed. Tried on 2 outlets each with a seperate run from the tap, but I see the exact same levels.

Signal levels were checked and balanced early last month due to weak downstream power at the time.

Location: Philadelphia, PA

Links to screenshots with requested info:

Signal levels

Error logs

Firmware info

SteveLiebler · ‎08-02-2012

For the "For what it's worth file":

I have a dual boot - Win 7 and Win Server 2008 R2. I just made the connection (no pun intended) that my SB6121 would stop responding on the WAN side of things while looking quite normal on the LAN side only when I booted to Win 7.

Using a laptop, I monitored the connection to the Internet via a ping -t www.google.com. In a very predicable fashion, every time I booted to Win 7, the ping times would deteriorate then lose connection connection altogether. The modem lights were normal, the status page was normal when I checked the modem at 192.168.100.1, the Airport Utility showed no Internet connection.

Shutting down Win 7 restored the connection and the "normal" ping times. This is without having to reset the modem.

Being the inquisitive person that I am, I started investigating what had been installed on the Windows box that wasn't on the Server 2008 box.

What I found was Google Drive for the PC was the culprit - I uninstalled Google Drive and I now have a reliable connection via the SB6121 modem. Every time I boot Windows 7.

Now, I am not sure if it is a bug Google Drive, or the fact that I had about 12GB of stuff being synced. I think the size of the files shouldn't really be an issue as I have used other applications (Dropbox, Mozy Home) with no connectivity issues. There must be something up with Google Drive's sync feature.

Anyway, this may or may not help but I just thought I would throw it out there just in case. I'll know for sure as the days pass and I stay connected after booting to Win 7 - hopefully.

cheers,

Steve

Basic Internet Connectivity And Modem Help

Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.

Re: Having issues with your Motorola SB6121? Please post here.