Skip to main content
abg's profile

abg

New Contributor

 • 

2 Messages

Closed

SB6141 Aborted upstream bonding channel ranging status.

For about the past 6 weeks or more we have had issues with our connection being very poor in the mornings, until about 9:00 or 10:00 AM local time. From then until after we go to bed it is fine. I have called the Cox support a few times, but it has proved fruitless, partly because I work during the times it is out, so I'm calling when everything is fine. I've seen similar issues to mine, but most indicate upstream power is too high, while mine is high 30's to low 40's.

During these issues anywhere from 1-3 channels have a ranging status of Aborted, and the logs generates the same 2 entries over and over again. A power cycle (power cord or UI initiated) almost always will fix the problem, though if it is in that window of pre 9:00 or 10:00 AM, it will usually fail again within less than 30 minutes or so. I have also had it come back up with some ranging status of Aborted.

I've included some data below from the Modem UI to help. 

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.14-SCM01-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 374781336021831310020022
Firmware Build Time: Mar 6 2014 15:23:55

Downstream Bonding Channel Value
Channel ID 75  73  74  76  81  82  83  84 
Frequency 825000000 Hz  813000000 Hz  819000000 Hz  831000000 Hz  861000000 Hz  867000000 Hz  873000000 Hz  879000000 Hz 
Signal to Noise Ratio 38 dB  37 dB  37 dB  37 dB  38 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
-1 dBmV   -1 dBmV   -1 dBmV   -1 dBmV   -1 dBmV   -2 dBmV   -2 dBmV   -2 dBmV  

Upstream Bonding Channel Value
Channel ID 4  1  2  3 
Frequency 36300000 Hz  18400000 Hz  23300000 Hz  29800000 Hz 
Ranging Service ID 9  9  9  9 
Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
Power Level 42 dBmV  40 dBmV  41 dBmV  42 dBmV 
Upstream Modulation [3] 16QAM
[3] 64QAM
 		 [3] QPSK
[2] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 
Ranging Status Success  Success  Aborted  Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 75  73  74  76  81  82  83  84 
Total Unerrored Codewords 1136663615  1136674596  1136683716  1136691836  1136659404  1136660934  1136663223  1136683471 
Total Correctable Codewords 71  27  58  125  241  179  175  383 
Total Uncorrectable Codewords 1593  1462  1403  1398  1521  1454  1644  1455 

Nov 05 2014 11:32:50

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:49

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:49

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:48

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:48

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:47

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:47

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:46

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:46

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:45

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:45

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:44

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:44

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:43

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:43

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:42

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:42

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:41

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:41

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

Nov 05 2014 11:32:40

3-Critical

R07.0

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[MAC ADDRESS];CMTS-MAC=[MAC ADDRESS];CM-QOS=1.1;CM-VER=3.0;

 Edit: Stripped out MAC addresses.


Discussions

 • 

Updated 

4.9K

3

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

I do see some T3 errors mentioned in your logs which would suggest an upstream communication problem.  Has this been a consistent problem or did it just start yesterday?

0

0

A

abg

New Contributor

 • 

2 Messages

It's been pretty consistent for about 6 - 8 weeks. Again, it only happens in the morning, until about 9-10 (though this example was until after 11:00 AM).

I only began looking at the logs about 3 weeks back and I've noticed the aborted channels and the associated errors in the logs. The power levels are always about where you see them now (39-41 range) on refreshes, though it's possible there are spikes that I don't see on a static web interface.

I have a total of 3 connectors from the outside to the modem, and I am planning to replace them all today. The outside one is a tap put there by a Cox contractor when we had our Cox phone service setup. The higher loss was routed to the phone with the lower loss signal going to the modem. The other 2 connectors are barrel connectors/couplers (one mid-line in a smart panel and 1 at the wall plate).

I plan on replacing all 3 with replacement barrel connectors. If there is any issue in the lines in my house, I'm suspect at the tap outside -- not because of signal loss (as you can see, signal is fine), but because of possible occassional failure in the tap itself. This goes to the only other thing that has changed in that 6-8 week window is that our AZ nights have been getting cooler (50s-60s) and it is in those cooler times that we notice the issue.

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

These types of issues are actually best addressed by a technician coming out.  If he/she determines that the problem still exists at the tap or beyond the matter would be escalated to our maintenance team for follow up.

0

0