Community Forum

Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

Regular Visitor

Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

I'm getting the Started Unicast/No Response message multiple times a minute on my Netgear CM700 modem:

 

Time

Priority

Description

2017-05-28, 11:42:51

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:44

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:44

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:44

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:43

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:43

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:43

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:43

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:43

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:43

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:21

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:42:00

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:37

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:37

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:37

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:36

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:36

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:36

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:36

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:36

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:36

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:15

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:15

Critical (3)

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

2017-05-28, 11:41:15

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=<mac address removed>;CMTS-MAC=<mac address removed>;CM-QOS=1.1;CM-VER=3.0;

 


Also, downstrean channels look okay but only one bonded upstream channel:

 

Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 705000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 17 705000000 Hz 0.8 dBmV 40.1 dB 0 0
2 Locked QAM256 1 609000000 Hz 2.6 dBmV 41.9 dB 0 0
3 Locked QAM256 2 615000000 Hz 2.8 dBmV 42.2 dB 0 0
4 Locked QAM256 3 621000000 Hz 2.1 dBmV 41.6 dB 0 0
5 Locked QAM256 4 627000000 Hz 2.6 dBmV 41.9 dB 0 0
6 Locked QAM256 5 633000000 Hz 2.2 dBmV 41.5 dB 0 0
7 Locked QAM256 6 639000000 Hz 2.3 dBmV 41.4 dB 0 0
8 Locked QAM256 7 645000000 Hz 1.9 dBmV 41.2 dB 0 0
9 Locked QAM256 8 651000000 Hz 2.2 dBmV 41.4 dB 0 0
10 Locked QAM256 9 657000000 Hz 1.7 dBmV 41.0 dB 0 0
11 Locked QAM256 10 663000000 Hz 1.7 dBmV 40.9 dB 0 0
12 Locked QAM256 11 669000000 Hz 1.7 dBmV 40.7 dB 0 0
13 Locked QAM256 12 675000000 Hz 1.6 dBmV 39.7 dB 0 0
14 Locked QAM256 13 681000000 Hz 1.0 dBmV 40.2 dB 0 0
15 Locked QAM256 14 687000000 Hz 0.8 dBmV 40.1 dB 0 0
16 Locked QAM256 15 693000000 Hz 1.3 dBmV 40.3 dB 0 0
17 Locked QAM256 16 699000000 Hz 1.1 dBmV 40.3 dB 0 0
18 Locked QAM256 18 711000000 Hz 0.6 dBmV 39.9 dB 0 0
19 Locked QAM256 19 717000000 Hz 0.6 dBmV 39.9 dB 0 0
20 Locked QAM256 20 723000000 Hz 0.6 dBmV 39.9 dB 0 0
21 Locked QAM256 21 729000000 Hz 0.2 dBmV 39.6 dB 0 0
22 Locked QAM256 22 735000000 Hz -0.3 dBmV 39.2 dB 0 0
23 Locked QAM256 23 741000000 Hz 0.1 dBmV 39.4 dB 0 0
24 Locked QAM256 24 747000000 Hz -0.8 dBmV 38.6 dB 0 0
 
<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 89 5120 Ksym/sec 35800000 Hz 44.3 dBmV
2 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
3 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

 

Finally, been doing DSLReports ping test and scored an F

I am getting Comcast 75/10 internet (no TV). The physical cable (from pole to house about 60-70 feet) is original Comcast buried from 2001. House interior cable is all RG6 quad, brand new with only the original ground blocks (Comcast early 2000, one at pole one at house) and wall plate between pole to cable modem. While checking all connections, noticed a cut next to plug on cable coming down pole from main Comcast cable right next to pole ground block. Cut off damaged cable (about 2 inches) and replaced plug but that had not impact.

 

I'm guessing service call, any other suggestions? This is in Tallahassee, FL.

Expert

Re: Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

The stats as read at the modem level at that moment in time were o/k but there are three additional signal stats that can cause those errors and the unbonding of channels which can't be read by the modem. They can only be read from their end by them polling the CMTS (Cable Modem Termination System) at the local headend facility.

They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.

You can call in and ask what these figures are. The Upstream Receive Power Level should fall within the range of -2dB to +2dB with 0dB being in the middle and perfect.

The Upstream SNR should be least 31dB, and the higher it is the better.

The ICFR should be no higher than 2 dB.

You could have an intermittent noise ingress issue in only the upstream channel(s) / return path only somewhere.

They will be able to see whether or not everything is in the green zone and also see a history plot for the modem.




I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Regular Visitor

Re: Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

Could the old buried coax be a possible issue? Just trying to knock down all possiblities on my end. I am tempted to take the modem and laptop out to pole and connect directly to the Comcast drop at the ground block there and see how it runs (modem stats and DSLReports speed/ping tests). Since the above messages are coming up as soon as the modem is connected, I'm guessing that would tell me pretty quickly that its the main feed versus any issues between house and pole (if error messages pop up right away). If it runs well there, I could then check where buried cable is connected to block on house side and see if there is issue at that point. That would tell me buried line is issue. If not, then it could be something in the new RG6 lines in house. 

Expert

Re: Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

You could give it a try just to see but I would recommend retrieving the levels EG asked for before doing that just to get the all the signal specs from that specific location.

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Regular Visitor

Re: Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

I'm including some photos of the damage I found on the cable drop on the pole from the Comcast mainline at the ground block that I mentioned in the first post. It looks like water got into the shielding and corroded it as well as the core. I cut back 2 inches from where I cut here and it also had some powdery corrosion on the shielding as well. I went ahead and put on a new compression F fitting. Besides calling in for the stats EG referenced, I wonder if I should call to get a new cable drop put in from the mainline. Hard telling how far up water could have wicked. I'm pretty sure that damage happened since we had a hurricane in Tallahassee last year. The wind blew the cable off the pole, but did not break it. At the time, while Comcast was in the neighborhood repairing storm damage, they reattached and checked the line and it was okay. I know I inspected it at the time and it did not have that cut then.

 

 

20170528_163545-1[1].jpg20170528_163709-1[1].jpg

Expert

Re: Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

Bottom line. Book a tech visit. They will determine what is needed. They won't automatically replace the drop unless they determine that it is actually needed. Good luck !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Regular Visitor

Re: Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

Well, alls well that ends well. Turned out there were lots of interesting things going on and was helped by some good support.

 

First, I had replaced our Arris SB6190 (Puma 6 chipset) with a Netgear CM600 (Broadcom chipset) because I thought I had some of the Puma 6 issues. Turned out the new CM600 had some kind of hardware issue and kept taking itself down, regardless of traffic. Logs had this coming up every few hours and as it approached connection would degrade. That was returned to Staples.

 

Second, after reinstalling SB6190, they pushed the V firmware and it seemed to help some things, but I was still getting a ton of bufferbloat and lag on DSLReport Speedtest, as well as a lot of the above error messages in OP. Turned out that the recommendations I had gotten from the official Roku forum on optomizing our Asus router were not necessarily right. One recommendation included turning off QoS in our router, which in fact was causing the bufferbloat and lag issue (which had been affecting our Roku stream). After turning QoS on and setting it to our speed level (75/10) the speed test numbers were golden AND our Roku is streaming like a champ.

 

Third, there was some upload signal issues that were attributed to the damaged cable. Instead of having a truck roll, I just cut 2 feet out and spliced it with some leftover R6 quad and grounding blocks I had from from OTA antenna install project, including replacing the old block that was corroded from water intrusion afrom damaged cable. After that numbers were good for upload signal quality. 

 

At the end of the day, our connection is golden and we are enjoying our internet. I would say that case is closed/solved.

Expert

Re: Started Unicast Maintenance Ranging - No Response received - T3 time (multiple times a minute)

Glad you got it straightened out !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!