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
•
Firmware for SB6141
I wanted to understand if I have the correct firmware for my modem.
I have the SB6141, and according to the Motorola User guide it says following:
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
But the cox telephone person I spoke in tier 2 level support said they had entered my modem as a "6180".
Infact they do not even have a SB6141 in their list of modems, but it is shown on the supported modems list.
What firmware needs to be used on SB6141 for Cox Service in Gilbert, Arizona
Current firmware (is this correct?)
Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Serial Number: 348781213800757006010001
Firmware Build Time: Apr 17 2012 15:09:37
Right now I get random disconnects. DOes this signal information look okay?
This page provides information about the current upstream and downstream signal status of your Cable Modem.
| Downstream | Bonding Channel Value | ||||||
|---|---|---|---|---|---|---|---|
| Channel ID | 97 | 98 | 99 | 103 | 104 | 105 | |
| Frequency | 825000000 Hz | 831000000 Hz | 837000000 Hz | 861000000 Hz | 867000000 Hz | 873000000 Hz | |
| Signal to Noise Ratio | 35 dB | 35 dB | 35 dB | 35 dB | 35 dB | 35 dB | |
| Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
|
-6 dBmV | -6 dBmV | -6 dBmV | -7 dBmV | -7 dBmV | -7 dBmV | |
| Upstream | Bonding Channel Value | |
|---|---|---|
| Channel ID | 3 | 1 |
| Frequency | 36100000 Hz | 23300000 Hz |
| Ranging Service ID | 6726 | 0 |
| Symbol Rate | 5.120 Msym/sec | 2.560 Msym/sec |
| Power Level | 53 dBmV | 51 dBmV |
| Upstream Modulation | [3] QPSK [3] 64QAM |
[3] QPSK [2] 16QAM [3] 64QAM |
| Ranging Status | Success | Success |
| Signal Stats (Codewords) | Bonding Channel Value | |||||
|---|---|---|---|---|---|---|
| Channel ID | 97 | 98 | 99 | 103 | 104 | 105 |
| Total Unerrored Codewords | 548608311 | 547575329 | 547567061 | 547583470 | 547562882 | 547564006 |
| Total Correctable Codewords | 6 | 46 | 44 | 17 | 34 | 20 |
| Total Uncorrectable Codewords | 549 | 507 | 506 | 568 | 664 | 617 |
Current Log:
| ct 02 2012 20:48:50 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 20:48:50 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:34 | 5-Warning | D04.1 | ToD request sent - No Response received;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;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=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;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=20:e5:64:5b:b5:7b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 20:46:54 | 3-Critical | R07.0 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 19:37:21 | 4-Error | E107.0 | SW upgrade Failed after download - Incompatible SW file |
| Oct 02 2012 19:36:54 | 6-Notice | E101.0 | SW Download INIT - Via NMS |
| Oct 02 2012 19:33:53 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 19:33:44 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 19:33:44 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:52 | 5-Warning | D04.1 | ToD request sent - No Response received;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:33 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:14 | 6-Notice | N/A | Cable Modem Reboot from SNMP ;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 19:32:24 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 19:32:24 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:27 | 5-Warning | D04.1 | ToD request sent - No Response received;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Jan 01 1970 00:00:14 | 6-Notice | N/A | Cable Modem Reboot from SNMP ;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 18:43:57 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
| Oct 02 2012 18:43:57 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:e5:64:5b:b5:7b;CMTS-MAC=00:1b:54:c9:03:c6;CM-QOS=1.1;CM-VER=3.0; |
ChrisL
Former Moderator
•
The firmware is the only version we have available for that modem as of now. The transmit power levels are out of specification on the high end suggesting there is a signal issue somewhere. It may be necessary for a technician to come out and troubleshoot at some point.
0
0
Firmware_for_SB
New Contributor
•
I have a tech coming out tomorrow to help troubleshoot.
What power level is out of spec, can you tell me? What # should it be, ?
0
0
Firmware_for_SB
New Contributor
•
I see!
The upstream power level is around 52,50 which would appear to be too high.
I hope the cox tech that comes tomorrow is able to diagnose.
DOCSIS 3.0 modems:
Downstream power level (Receive): -15dbmV to +15dbmV
A value of -10 or worse indicates a poor downstream signal path. A tech would aim for a value close to the optimal 0 dBmV, but a good cable modem should be capable of working within the broader range of -10 to +10 dBmV, provided the downstream Signal to Noise Ratio remains good enough. Additionally all downstream channels should be within a +/-2db window with respect to each other.
Upstream (Transmit): 40-52 dBmV. A value within the range +40 to +52 dBmV is within spec with the low to mid 40's the most common. If the cable modem is going offline, and the upstream signal strength is at or above +52dBmV, then a poor upstream path is probably the problem.
Carrier/Noise Ratio: 35 db and above The downstream Signal to Noise Ratio must be 35 dB or higher on each channel. The lower ratio the more noise and the poorer the performance. The Cable Modem will have to keep requesting retransmissions of packets with uncorrectable errors.
0
0
Firmware_for_SB
New Contributor
•
Cox guy came out today, was very friendly, and found I had way old infrastructure.
I was connected to the old phone service which he said was known to cause high interference transmit levels.
Also he found all types of old fittings, old splitters.
Removed all that ** , and here are my new signal levels, thanks cox!
This page provides information about the current upstream and downstream signal status of your Cable Modem.
[3] 64QAM
[2] 16QAM
[3] 64QAM
[3] 64QAM
0
0