Apr 22 2013 19:21:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:52:57 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:52:57 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:52:13 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:51:43 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:51:17 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:51:12 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 18:50:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:57:18 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:57:05 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:57:02 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:56:52 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:56:52 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:54:23 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:53:44 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:53:20 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:53:00 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 22 2013 17:51:36 5-Warning T202.0 Lost MDD Timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;

actions · 2013-Apr-22 10:27 pm ·

Le Roy

2 edits

Le Roy

Premium Member

2013-Apr-23 1:17 pm

Apr 23 2013 11:11:11 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 11:11:11 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:47 5-Warning R09.0 B-INIT-RNG Failure - Retries exceeded;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:08:01 3-Critical D01.0 DHCP FAILED - Discover sent, no offer received;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:07:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:54 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:42 5-Warning T203.0 MDD message timeout;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 11:00:01 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 03:05:35 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:54:25 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:54:25 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:53:41 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:52:56 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:41:40 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;
Apr 23 2013 02:41:40 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:7c:bf;CMTS-MAC=00:26:99:8a:99:9e;CM-QOS=1.1;CM-VER=3.0;

This time the connection went down for a while. Like 15 - 20 minutes before the modem would connect again, power cycling seemed to have no effect. I was on the phone with the CO when it was down and when it came back online, he told me over the phone that he didn't see the modem online, despite it being online on my end. Weird. They are sending another tech out, right now he's talking to one of the techs in the call center apparently.

edit
He said they had an outage on their end, which is the reason why he wasn't able to see the modem come back online and the reason why it was off for so long. He said he still seen prior connection drops on my line and he's going to send a tech out anyway, so one will be here tomorrow between 3 - 5P.

actions · 2013-Apr-23 1:17 pm ·

Le Roy

Le Roy

Premium Member

2013-Apr-24 5:39 pm

Well now I will find out if it's the cable modem or something on their end. They left an SB6180 here on the same line as my SB6141, both are connected to the same 3 way splitter and online. So in theory, if it's a problem on their end, both modems should go down; but if it's the SB6141 modem, then only it will go down.

actions · 2013-Apr-24 5:39 pm ·

swintec
Premium Member
join:2003-12-19
Alfred, ME

swintec

Premium Member

2013-Apr-24 5:49 pm

said by Le Roy:

The problem is the T4 timeouts you are having. Granted, you arent supposed to get them but if they do happen the firmware that your (and many others) 6141's run on will cause the modem to drop like you see.

My 6141 runs great with the same firmware that yours has...but I do not have cable plant issues so i do not get T4 errors.

I think in this case, it is hard to pin blame. One side would say the modem should handle the T4 errors more gracefully. The opposite side would say the cable plant should be addressed so T4 errors should not happen to begin with.

At any rate, firmware revisions put out by Motorola address this. Maybe your cable company is small enough where you can get them to apply a more recent version for you and others on the network. I see it as a bandaid fix though for the bigger issue but I guess it is the easiest thing to do rather than have them track down why the T4 issue is happening to begin with.

actions · 2013-Apr-24 5:49 pm ·

Le Roy
Skillz
Premium Member
join:2002-05-03
Ocean Springs, MS

Le Roy

Premium Member

2013-Apr-24 5:59 pm

So what you are saying is what I am fearing. They are going to come back and say it's a problem with my Cable Modem since the 6180 wont be getting dropped when the 6141 will? If I tell the line tech who is coming back to my house tomorrow that the reason why the 6141 is dropping it's connection is because of T4 errors. The problem is, the 6141 is not "officially" supported by my Cable Company (Cable One) so they will most likely just tell me to get a new cable modem.

Worst case scenario, I do have to get a new one. Which one would be recommended?

actions · 2013-Apr-24 5:59 pm ·

swintec
Premium Member
join:2003-12-19
Alfred, ME

swintec

Premium Member

2013-Apr-24 6:07 pm

said by Le Roy:

The problem is, the 6141 is not "officially" supported by my Cable Company (Cable One) so they will most likely just tell me to get a new cable modem.

What modems are supported by your cable company? The 6141 uses the same firmware as the 6121 and I believe the 6120. This was by design by Motorola in order to make things a bit easier on ISPs. If they utilize either of those modems as supported they should have no problem supporting the 6141, or at least upgrading you to a newer firmware (although i realize this would be an uphill battle for you on that front).

There is a white 6141 available now through regular retail channels (Newegg, etc) that ships with a newer firmware. This should take care of your issue. My experience on this front simply comes from discussions in the Time Warner forum and users posting about it. YMMV on a different cable company but your symptoms are all the same.

actions · 2013-Apr-24 6:07 pm ·

Le Roy
Skillz
Premium Member
join:2002-05-03
Ocean Springs, MS

Le Roy

Premium Member

2013-Apr-24 6:11 pm

Oh wow, I just looked up the latest support list and the 6141 has been added!! When I bought the modem back in January, it wasn't listed.

»support.cableone.net/app ··· m-models

That's good to know, so the 6180 uses the same firmware as well? If not, then I am afraid they are still going to tell me it's my modems problem when the 6180 they left here wont be getting dropped.

On the other hand, if it does have the same firmware and it does get dropped, that should make it a lot easier to tell them they need to update their firmware to solve the problem.

Do you happen to have some more documentation/links that I can read more into this so I can be better educated on the issue for when the tech comes back out tomorrow?

actions · 2013-Apr-24 6:11 pm ·

swintec
Premium Member
join:2003-12-19
Alfred, ME

swintec

Premium Member

2013-Apr-24 6:33 pm

said by Le Roy:

That's good to know, so the 6180 uses the same firmware as well? If not, then I am afraid they are still going to tell me it's my modems problem when the 6180 they left here wont be getting dropped.

No, the 6180 does not share the same firmware image. Just the 6141, 6121 and 6120.

Key part from the manual linked to below:
"Easily add the SB6141 to a deployed family of SB6120s and SB6121s, all three models utilize the same firmware image. This reduces qualification time for an Operator and eliminates configuration management headaches."

»moto.arrisi.com/staticfi ··· S-EN.pdf

actions · 2013-Apr-24 6:33 pm ·

Le Roy
Skillz
Premium Member
join:2002-05-03
Ocean Springs, MS

Le Roy

Premium Member

2013-May-1 11:23 pm

Well so far I haven't had any connection issues with the modem.

actions · 2013-May-1 11:23 pm ·

Le Roy

1 edit

Le Roy to Meatball

Premium Member

2013-May-5 5:31 am

to Meatball

Re: SB6141 Firmware Update?

Spoke too soon. Seems as long as I don't upload anything heavily and/or download constantly I am fine. Once I start using the connection I pay for, I get those errors and the modem reboots itself.

Maybe this will be of some help.

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.10-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: xxxxxxxxxxx
Firmware Build Time: Oct 29 2012 18:07:13

actions · 2013-May-5 5:31 am ·

ShudderUser
join:2013-05-26
Charlotte, NC

ShudderUser to permutations

Member

2013-May-26 1:11 pm

to permutations

"Meatball", and friends,
I Shudder here in Charlotte, NC. Switching to TWC from ATT Uverse to gain control of my home network (silly me for wanting to manage VoIP & NOT pay $35/mo to ATT).

ANYWAY, looking to you as I prepare to buy my own modem and router. After reading about Meatball's experience with Motorola's still-approved, purchased router since December, I wanted to cry (for us both, I promise!)

My eagerly-awaited departure (think "Argo" hostage) from AT&T ("I can transfer you to the Fee-based customer service area that can assist you with your issue"... ON A RENTED ROUTER? UGH!) Dear, dear Meatball: do you have any newer experiences? I see that one respondant suggested s/he had switched to a router not specifically "supported" by TWC. I find that move terrifying ... which is probably silly on my part.

I initially switched to ATT 2 years ago since it was easier to get them to initiate a simple reboot by calling an automated attendant: Can TWC do that now? I even chose their $6/mo (ironically, Motorola!) modem (they provide one already capable of wifi to addict the user and those pesky Phone ports mean they control your access to VoIP). They've taking the "User's Manual" off the FCC's website, but hey? It's not like I'm paying them rent to ... oh, wait, I am. Although you can access the router's [2Wire] web interface and change settings on the Ethernet ports, you can't really. I esp loved being taunted with the bright green "Contratulations! Successfully changed!" page they forgot to disable. Yes, even the interface lies to me.

Because TWC allows me to go month to month, I still prefer them. Would you suggest that I [suck it up and] rent the modem to get the access into my home with their alleged support and just purchase a router for wifi, VoIP and ethernet?

Peace and condolences as I Shudder in Charlotte.

actions · 2013-May-26 1:11 pm ·

boe_d
join:2003-10-12
Los Angeles, CA

boe_d

Member

2013-Jun-3 11:13 pm

I just switched out my TW rental unit for the Sb16141. I went from 26mbit down x 2mbit up to 3mbit down x2mbit up. I certainly am hoping this is fixed quickly.

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Firmware Build Time: Aug 18 2011 10:27:53

actions · 2013-Jun-3 11:13 pm ·

boe_d

boe_d

Member

2013-Jun-4 12:36 am

I've spent 2 hours working with TW. My old modem gets 26mbit down the best they can do for me is 15mbit.

actions · 2013-Jun-4 12:36 am ·

Le Roy
Skillz
Premium Member
join:2002-05-03
Ocean Springs, MS

Le Roy to Meatball

Premium Member

2013-Jun-13 8:33 am

to Meatball

Still having issues with T4 timeouts, but either I'm not using my Internet as much as I was before or it just doesn't happen as frequently.

Last night between 930PM and 1130PM, my modem rebooted due to T4 errors 4 times.

actions · 2013-Jun-13 8:33 am ·

Meatball
join:2006-03-26

Meatball

Member

2013-Jun-13 9:14 pm

Just want to say, I've been using the SB6121 (Firmware SB612X-1.0.5.1-SCM00-NOSH from Dec 2010) for months without a single issue. I know they fixed something in my neighborhood, but I also wonder if the 6141 just has issues with TWC's network.

actions · 2013-Jun-13 9:14 pm ·

Andrew LB
join:2005-10-10
Seal Beach, CA

Andrew LB

Member

2013-Jun-15 4:49 pm

Well I've been having this T4 timeout problem since last summer and have spent at least 20 hours arguing with TWC to get things fixed. It's hilarious that when I purchased my SB6141, I specifically asked TWC if I will receive full support for the modem since it is on their approved list, which they said they would.

Now they're telling me that they cannot even give me level 3 tech support because they don't support customer modems and that the problem is not on their end, but they'd like to send a tech out.... again.

They also told me that any firmware updates must be obtained from Motorola since this is a customer owned device.... so much for support.

Has anyone been able to get firmware from Motorola?

here is my current software:

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Firmware Build Time: Aug 18 2011 10:27:53

actions · 2013-Jun-15 4:49 pm ·

swintec
Premium Member
join:2003-12-19
Alfred, ME

swintec

Premium Member

2013-Jun-15 4:55 pm

How arte you approaching the problem with TW? T4 errors shouldnt happen under ideal circumstances so maybe it would be better to pursue that route? Obviously a modem shouldnt restart because of it but they do not seem willing to address that with a simple firmware update. FWIW, I have the same firmware but do not see the problem at all.

Maybe start a topic in the direct forum here and get the ball rolling for a widespread rollout of the newest firmware, which HAS been issued in some divisions according to some topics here. Or maybe they can at least get the T4 problems fixed.

actions · 2013-Jun-15 4:55 pm ·

Bob 3965
@mycingular.net

Bob 3965 to Meatball

Anon

2013-Jun-26 9:28 am

to Meatball

Does anyone from Motorola and TWC read these posts and try to fix these problems? After 6 pages of complaints it doesn't appear they care at all about their customers. I say class action lawsuit about false advertising and fraud for claiming everything is available on demand.

actions · 2013-Jun-26 9:28 am ·

DOCSIS Modem
@comcast.net

DOCSIS Modem

Anon

2013-Jun-26 1:32 pm

said by Bob 3965 :

Actually, only TWC can do anything about the problem. Motorola can not supply the end user with the firmware because only allowing the ISP to install firmware is part of the DOCSIS standard. The assumption is that an ISP will want to keep the firmware up to date on their customers' equipment, but apparently TWC just doesn't give a damn.

actions · 2013-Jun-26 1:32 pm ·

PCInTech
keeping art alive since 1953
Premium Member
join:2004-06-07
Massena, NY

PCInTech to swintec

Premium Member

2013-Jun-29 8:42 am

to swintec

I also have the 1.0.6.3 firmware, without issues.

actions · 2013-Jun-29 8:42 am ·

Mele20
Premium Member
join:2001-06-05
Hilo, HI

Mele20 to Bob 3965

Premium Member

2013-Jul-2 9:34 am

to Bob 3965

I have the Surboard 6141. It is leased. Oceanic TWC updated the firmware from the Aug 2011 that it came with (it was a brand new modem when they gave it to me last November when I upgraded to 20/2 on a one year special) a few weeks ago.

Another Oceanic user on the other side of this island recently bought his own 6121. It was flashed newer firmware by Oceanic although it was not the current SB_KOMODO-1.0.6.12-SCM00-NOSH that I was flashed. He's checking into why his was not flashed the same as mine as both Surfboards use the same firmware. At any rate, Oceanic DID flash newer firmware to a USER OWNED modem very recently. So, it is not true that TWC never flashes user owned modems with newer firmware.

My understanding is that TWC is gradually flashing the latest firmware for the 6141 and 6121 across the nation to both user owned and leased modems.

actions · 2013-Jul-2 9:34 am ·

BaldEagle
join:2000-12-12
Raleigh, NC

BaldEagle to Meatball

Member

2013-Jul-23 1:07 am

to Meatball

Dear Friends,
Since the title of this thread pertains to SB6141 Firmware Updates, I respectfully submit the following information:

On Saturday, 20 July 2013, I went to BestBuys and found about 7 Motorola SB-6141 WHITE plastic Cable Modems on the shelf. I went thru all 7, and finally found the box with the highest serial number (hence, the most recently manufactured product). I purchased it and took it home. The next night, I connected it to the TWC cable line, to the desktop, and then turned it on. I carefully opened my browser to "192.168.100.1" without the "http://" prefix, and immediately found the following, under the HELP tab:

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.12-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 374781314720292409020022
Firmware Build Time: Mar 12 2013 17:48:19

This page provides an overview of the Modem Configuration Manager, and brief troubleshooting information. The help here is applicable only to the Cable Modem functionality.

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

I then tried to connect to the Internet without success, and got a pop-up page telling me what my MAC number was, and to call TWC immediately, to register my Modem, which I did. I wound up talking to the "TWC National Help Desk" (in the Philipines), and was asked only for my model number, and MAC address. I was not asked for a Serial Number.

I asked if I had been CAPPED, because about 3 months ago, my old reliable Motorola SB-5100 had stopped going above 20Mbits/s, and I was told twice that TWC did not CAP anyone.

I have double checked my HELP page constantly since, waiting for my Firmware to be "downgraded", but this has not happened, nor do I think it will...

No reboots,
Downstream Signal to Noise Level = 37 dB on all 4 channels
Downstream Power Level = 1 dBmV
Upstream Power Level = 35 dBmV

Knock on wood. . .

Sorry for the long winded post, but it looks like the current release is 1.0.6.12 dated 12 March 2013.

P.S.
Target has the same SB-6141 for $89 retail, which is $10 cheaper than BestBuy.

--End--

actions · 2013-Jul-23 1:07 am ·

dark_star
join:2003-11-14
Louisville

dark_star

Member

2013-Aug-9 1:48 am

said by BaldEagle:

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.12-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 374781314720292409020022
Firmware Build Time: Mar 12 2013 17:48:19

I have the same modem, with identical firmware. I am still getting reboots.

actions · 2013-Aug-9 1:48 am ·

TwiztedZero
Nine Zero Burp Nine Six
Premium Member
join:2011-03-31
Toronto, ON

TwiztedZero

Premium Member

2013-Aug-12 5:04 pm

Hey any of you guys got the release notes for the SB_KOMODO-1.0.6.12-SCM00-NOSH firmware? We're kneen to get hold of any information you can pass on.

Thanks.

actions · 2013-Aug-12 5:04 pm ·

bp0
join:2013-08-12
Louisville, KY

bp0 to dark_star

Member

2013-Aug-12 9:27 pm

to dark_star

I'm also in Louisville and have been having these disconnects for the past 2 months. What part of town are you in? I'm wondering if a certain area is effected.

actions · 2013-Aug-12 9:27 pm ·

your moderator at work

scivi92
join:2013-08-23
North Royalton, OH

scivi92 to TwiztedZero

Member

2013-Aug-23 9:18 am

to TwiztedZero

Re: SB6141 Firmware Update?

said by TwiztedZero:

Hey any of you guys got the release notes for the SB_KOMODO-1.0.6.12-SCM00-NOSH firmware? We're kneen to get hold of any information you can pass on. Thanks.

Defects Fixed:
- An issue in which the SB6141 would reject a non-standard RCC based upon the order of the 8 downstream channels were advertised has been resolved. (SB-2839)
- The SBCM no longer has a 32 channel limit in the MDD database for the maximum size of the upstream channel list. Previously if more than 32 upstream were present in the MDD channel list, the SBCM would reject the MDD and come up in un-bonded mode. (SB-2846)
- The Copyright text now shows Motorola Mobility, LLC instead of Motorola Mobility, Inc. (SB-2847)

actions · 2013-Aug-23 9:18 am ·

Packeteers
Premium Member
join:2005-06-18
Forest Hills, NY

Asus RT-AC3100
(Software) Asuswrt-Merlin

1 edit

Packeteers to Meatball

Premium Member

2013-Oct-8 3:18 pm

to Meatball

got this modem installed a week ago from NewEgg;
Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.12-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 3747...
Firmware Build Time: Mar 12 2013 17:48:19
Time Warner Cable: Standard 15/1 service plan;
Signal to Noise Ratio 39 dB
Power Level 9 dBmV
Channel Binding: 8 Downstream / 4 Upstream
the only new item on my Logs tab is a normal;
Code:D106.0 DHCP Renew

My old sb5101u kept rebooting during >50% utilization for 10 minutes, so before asking for a premise visit, I decided to try a new better modem - and so far I'm glad i did. I hope this helps someone here

actions · 2013-Oct-8 3:18 pm ·

TWC23Mbs
@rr.com

TWC23Mbs

Anon

2013-Oct-10 4:23 am

Temporary success

Ditto on most everything said here... Time Warner Cable just replaced my Cisco with a Motorola SB6141 modem.

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.12-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 3487xxxx
Firmware Build Time: Mar 12 2013 17:48:19

I created a case ID and have a truck scheduled to come out tomorrow... but I did one last change that seemed to work:

* replaced the coax between the wall and my modem *

Modem worked continuously for the past 3 hours since that change... previously it would reboot/disconnect much more often (with both Cisco and Motorola).

I'll try updating later if any problems/success

actions · 2013-Oct-10 4:23 am ·

Forums → Equipment Support → Hardware By Brand → ARRIS/SURFboard	« NVG510, IP Passthrough, Time Capsule, and DHCPS-fixed • Motorola SB6121 mystery drops »
prev · 1 · 2 · 3 · 4 · 5 · next