SB 6141 Question

[jan191976]

I was looking at my modem log and see the following daily.

"Unicast Maintenance Ranging attempted - No response - Retries exhausted"

Is this something I should look into or call Time Warner about?

[MsRaye]

Copy and paste the modems signal level and error log pages and your zip... need more info.

[jan191976]

My Zipcode is 14120

Cant seem to figure out how to add attachment in this forum.

Downstream Bonding Channel Value
Channel ID 1 2 3 4 5 6 7 8
Frequency 699000000 Hz 705000000 Hz 711000000 Hz 717000000 Hz 723000000 Hz 729000000 Hz 735000000 Hz 741000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB 38 dB 37 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 1 dBmV 2 dBmV 2 dBmV 2 dBmV 2 dBmV 2 dBmV
Upstream Bonding Channel Value
Channel ID 12 9 10 11
Frequency 37000000 Hz 19400000 Hz 24200000 Hz 30600000 Hz
Ranging Service ID 14169 14169 14169 14169
Symbol Rate 2.560 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec
Power Level 48 dBmV 47 dBmV 47 dBmV 47 dBmV
Upstream Modulation [3] QPSK
[2] 16QAM
[3] QPSK
[2] 16QAM
[3] QPSK
[3] 16QAM
[3] QPSK
[3] 16QAM

Ranging Status Success Success Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 1 2 3 4 5 6 7 8
Total Unerrored Codewords 110436548103 28831179353 28831185779 28831194109 28831153365 28831141516 28831160921 28831129535
Total Correctable Codewords 20644 18461 18937 17701 21070 22959 25101 25464
Total Uncorrectable Codewords 67003 48636 49924 51039 68511 81258 86692 85307

Jan 26 2016 01:16:50 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 26 2016 01:16:50 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 26 2016 01:16:49 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 25 2016 06:23:44 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 25 2016 06:23:44 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 25 2016 06:23:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 23 2016 07:37:08 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 23 2016 07:37:08 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 23 2016 07:37:06 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2016 22:06:19 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2016 22:06:19 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 22 2016 22:06:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 01:15:39 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 01:15:39 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 01:15:38 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;
Jan 20 2016 12:05:20 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:ce:79:d9;CMTS-MAC=00:01:5c:48:32:58;CM-QOS=1.1;CM-VER=3.0;

[agentx5]

First some info now that I'm off work and before I leave the office...

Upstream

37.00 Mhz	TDMA	48.2 dBmv	38.1 dB
19.40 Mhz	TDMA	46.8 dBmv	36.2 dB
24.20 Mhz	ATDMA	46.8 dBmv	34.8 dB
30.60 Mhz	ATDMA	47.3 dBmv	36.4 dB

Downstream

699.00 Mhz	QAM256	0.6 dBmv	36.8 dB
741.00 Mhz	QAM256	2.5 dBmv	37.6 dB
735.00 Mhz	QAM256	2.5 dBmv	37.3 dB
729.00 Mhz	QAM256	2.1 dBmv	37 dB
723.00 Mhz	QAM256	2.1 dBmv	37.9 dB
717.00 Mhz	QAM256	2.2 dBmv	37 dB
711.00 Mhz	QAM256	1.4 dBmv	37 dB
705.00 Mhz	QAM256	0.5 dBmv	37 dB

Little easier to see now? ^_^  You can read my topic here if you want to know how to intepret those.

Last Flap

4 months ago

Makes me wonder...

Make Model Hardware Version Boot Version

Motorola

SB6141

7.0

PSPU-Boot(25CLK) 1.0.12.18m3

File Current Version

SB_KOMODO-1.0.6.14-SCM01-NOSH.NNDMN.p7.twc_signed

SB_KOMODO-1.0.6.14-SCM01-NOSH

The corrected and uncorrected errors are actually a low % if you do the math.  Not an issue in your case.

So your question?

"Unicast Maintenance Ranging attempted - No response - Retries exhausted"

That's the CMTS trying to update your modem or the modem trying to get an update from the CMTS and it's failing for some reason

The solution is so simple you might laugh at me: reboot the modem
(if TWC's servers aren't doing the auto-reboot you can always help them out by "powercycling" the modem).

If this starts to become a pattern however, a routine, then you might want to call us to have signals (we call them "hits") sent to refresh the modem and check the service codes on the account to make sure they are actually up-to-date for 2016.

I wouldn't stress failed maintenance update requests unless an issue comes from it.
/me holds up sign saying "DON'T PANIC!"

[MsRaye]

Uncorrectables shouldn't be higher than correctables, unable to tell if they're recent or a month ago. Reset the fec counters to 0 and check them again 6 hours later.

[jaison]

I would pass out if i had that many errored and corrected codewords.

[MsRaye]

It's not bad vs the total bytes, however, uncorrectables are bad, especially when they outnumber correctables which are fixed on the retry. Uncorrectables are dropped and require renegotiation all the way to the host server.

Correctables are fixed by the CM to CMTS  and don't go back thru any hops.

[agentx5]

---

@jaison wrote:

I would pass out if i had that many errored and corrected codewords.

---

MsRaye is correct.  That quantity versus the total number isn't actually a bad %.  And it's hard to tell if it's a current issue, because it's been soooo long since the counters were last reset.

[jaison]

Regardless of the amount, If you have a significat amount of  any there is still an underlying issue that needs addressed.

[MsRaye]

1 in 10 million is very acceptable