Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
SB 6141 firmware
this post needs to be removed due to mac and serial number info being posted
Forum: Internet Forum
Posted: 4 Mar 2015
Post Subject: SB 6141 firmware
Post author: g-naps
I purchased a brand new white Motorola SB 6141 in November. Everything was running great with it until mid to late January. Since then at least once a week the modem reboots itself. Ive had 2 techs out in the last 2 weeks and they say everything is fine with the line. In fact the one that was out today said that the modem has been up for 22 days. I showed him the logs on the modem where there are t4 timeouts and reboots as recent as yesterday. I was told it could be due to the RG59 cabling in my unit. I find this hard to believe since in the 12+ years Ive lived here I can count on 1 hand the number of times Ive had internet issues.
Ive read that there is updated firmware available but everyone Ive spoken on the phone says theres no update available. Is the firmware only available to certain regions?
The current firmware on my modem:
SB_KOMODO-1.0.6.12-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 374781421200029210020022
Firmware Build Time: Mar 12 2013 17:48:19
Most recent logs from the modem:
|
Mar 03 2015 17:33:01 |
6-Notice |
I401.0 |
TLV-11 - unrecognized OID;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Mar 03 2015 17:33:01 |
5-Warning |
Z00.0 |
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Jan 01 1970 00:00:15 |
6-Notice |
N/A |
Cable Modem Reboot due to T4 timeout ;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Mar 03 2015 17:32:17 |
3-Critical |
R04.0 |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Mar 03 2015 17:29:22 |
3-Critical |
R02.0 |
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Mar 03 2015 17:29:22 |
3-Critical |
R07.0 |
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Mar 03 2015 17:29:21 |
3-Critical |
R02.0 |
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Mar 03 2015 17:29:21 |
3-Critical |
R07.0 |
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |
|
Mar 03 2015 17:29:20 |
3-Critical |
R02.0 |
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:4b:d0;CMTS-MAC=68:ef:bd:85:9a:b3;CM-QOS=1.1;CM-VER=3.0; |