Skip to main content
sp1000's profile

sp1000

New Contributor

 • 

5 Messages

Closed

sb6141 drops off line several times daily

I have been struggling to get my Preferred Level Internet service working reliably since June 2015. The previous DOCSIS 2.0 modem supplied by COX failed repeatedly in staying connected, and I was told to change the Modem to DOCSIS 3.0. Cox techs have inspected my cables and replaced the entire connection from the distribution box in the street all the way inside. However, even with all new cables and new Arris SB6141 and new Netgear router, the internet connection still fails abruptly whenever it feels like. When it works, it works well (60 up, 7 down). It is, however, always restored with a power off and a restart. Lots of other customers on this forum have requested a firm ware upgrade for this model of modem. Could this be the problem for mine, as well?

Discussions

 • 

Updated 

3K

6

0

0

T

Tecknowhelp

Valued Contributor II

 • 

2.8K Messages

What are your signal levels? Also what do the logs say? Should be able to find that data at 192.168.100.1 of the modem. 

Also, when the connection fails. Is it all devices? Wireless? Do you still see the network?

0

0

S

sp1000

New Contributor

 • 

5 Messages

Tecknowhelp said:

What are your signal levels? Also what do the logs say? Should be able to find that data at 192.168.100.1 of the modem. 

Also, when the connection fails. Is it all devices? Wireless? Do you still see the network?

When the modem works, I get 50+ down and 6 + up, which are the levels provided by COX for my service, and I am not complaining; but, yes, both my wired desktop machine, VOIP phone, and all wireless devices feeding off the router get no connection, once the modem decides to quit. When it does this, all the panel lights stay on normally. I don't know how to pull the logs data and paste it here.

0

0

S

sp1000

New Contributor

 • 

5 Messages

sp1000@cox.net said:
Tecknowhelp said:

What are your signal levels? Also what do the logs say? Should be able to find that data at 192.168.100.1 of the modem. 

Also, when the connection fails. Is it all devices? Wireless? Do you still see the network?

When the modem works, I get 50+ down and 6 + up, which are the levels provided by COX for my service, and I am not complaining; but, yes, both my wired desktop machine, VOIP phone, and all wireless devices feeding off the router get no connection, once the modem decides to quit. When it does this, all the panel lights stay on normally. I don't know how to pull the logs data and paste it here.
Nov 28 2015 18:32:56 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 18:32:56 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:45 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:44 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:42 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:42 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:41 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:41 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:40 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:39 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:38 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:38 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0; Nov 28 2015 15:19:37 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:42:e3:c3;CMTS-MAC=00:1b:54:c9:a5:c7;CM-QOS=1.1;CM-VER=3.0;

0

0

T

Tecknowhelp

Valued Contributor II

 • 

2.8K Messages

sp1000@cox.net said:
No Ranging Response received - T3 time-out

I see some T3 errors. Usually they are caused by upstream problems. Can you post your signal levels?

0

0

S

sp1000

New Contributor

 • 

5 Messages

Tecknowhelp said:

sp1000@cox.net said:
No Ranging Response received - T3 time-out

I see some T3 errors. Usually they are caused by upstream problems. Can you post your signal levels?

http://192.168.100.1/cmSignal.htm Channel ID 73 74 75 76 81 82 83 84 Frequency 813000000 Hz 819000000 Hz 825000000 Hz 831000000 Hz 861000000 Hz 867000000 Hz 873000000 Hz 879000000 Hz Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB 37 dB 38 dB 38 dB 37 dB Downstream Modulation QAM256 QAM256 QAM256 QAM256 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 1 dBmV 0 dBmV 0 dBmV 0 dBmV 0 dBmV Upstream Bonding Channel Value Channel ID 1 2 3 4 Frequency 37104000 Hz 30704000 Hz 23696000 Hz 18896000 Hz Ranging Service ID 1994 1994 1994 1994 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level 44 dBmV 44 dBmV 44 dBmV 42 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] QPSK [2] 16QAM [3] 64QAM Ranging Status Success Success Success Success

0

0

S

sp1000

New Contributor

 • 

5 Messages

sp1000@cox.net said:
Tecknowhelp said:

sp1000@cox.net said:
No Ranging Response received - T3 time-out

I see some T3 errors. Usually they are caused by upstream problems. Can you post your signal levels?

http://192.168.100.1/cmSignal.htm Channel ID 73 74 75 76 81 82 83 84 Frequency 813000000 Hz 819000000 Hz 825000000 Hz 831000000 Hz 861000000 Hz 867000000 Hz 873000000 Hz 879000000 Hz Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB 37 dB 38 dB 38 dB 37 dB Downstream Modulation QAM256 QAM256 QAM256 QAM256 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 1 dBmV 0 dBmV 0 dBmV 0 dBmV 0 dBmV Upstream Bonding Channel Value Channel ID 1 2 3 4 Frequency 37104000 Hz 30704000 Hz 23696000 Hz 18896000 Hz Ranging Service ID 1994 1994 1994 1994 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level 44 dBmV 44 dBmV 44 dBmV 42 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] QPSK [2] 16QAM [3] 64QAM Ranging Status Success Success Success Success
A COX tech came by this afternoon, and confirmed that the cable was OK all the way to the modem; he contacted tech support who found that the modem has had several input power adjustments, possibly caused by a faulty AC adapter. It is supposed to put out 12V DC, but testing it with a multimeter showed 14 V to 16V; I am thinking that this high voltage my cause the modem to shut off to prevent damage if it gets too hot. I found another AC adapter with similar or better output and replaced it. So far, so good......

0

0