cancel
Showing results for 
Search instead for 
Did you mean: 

Broadband Dropping - No Ranging Response received - T3 time-out

bittnerbarni
Joining in

Hey, 

So my broadband started dropping out a few weeks ago. It started with no service for an hour or so, in a day, now it has gotten to the point of losing packages almost all the time, and having no service for hours intermittently.

Also, my broadband speed is supposed to be ~200Mbps, yet measuring it via Speedtest.net I only get ~65-67Mbps. Measured it via direct connection to PC via ethernet cable, and also through wifi (5GHz, Netgear R7000 Router connected to CM via ethernet) on a 2017 Macbook pro.

Network Log:

Spoiler

Time

Priority

Description

04/09/2021 19:50:40

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:50:39

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:50:20

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:50:19

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:49:40

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:49:40

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:48:20

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:48:20

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:46:5

notice

LAN login Success;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:45:40

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:45:40

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:44:19

notice

LAN login Success;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:37:41

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:36:21

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:36:21

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:36:1

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:36:1

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:15:23

critical

No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/09/2021 19:15:23

critical

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Downstream Channels:

Spoiler
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1330750000-12.236256 qam25
2202750000-7.238256 qam9
3210750000-7.938256 qam10
4218750000-7.538256 qam11
5226750000-8.937256 qam12
6234750000-10.537256 qam13
7242750000-10.737256 qam14
8250750000-9.538256 qam15
9258750000-10.737256 qam16
10266750000-11.437256 qam17
11274750000-10.237256 qam18
12282750000-8.238256 qam19
13290750000-1037256 qam20
14298750000-11.936256 qam21
15306750000-1037256 qam22
16314750000-8.238256 qam23
17322750000-10.236256 qam24
18338750000-11.436256 qam26
19346750000-8.737256 qam27
20354750000-8.737256 qam28
21362750000-1236256 qam29
22370750000-13.835256 qam30
23378750000-12.236256 qam31
24386750000-11.736256 qam32

Upstream Channels (aren't Power Levels off the charts?):

Spoiler
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
13260000048.3512032 qam5
24620000047512032 qam3
35370000046.3512032 qam2

 

 

 

5 REPLIES 5

Tudor
Very Insightful Person
Very Insightful Person

Most downstream channels have a too high a power level and you have 3 instead of 4 upstream channels that are on 32 not 64 QAM. You probably need a technician’s visit 

Check with Area faults on  0800 561 0061 or if you have a VM landline 150

If no faults found:

Call Customer Services on 0345 454 1111 or if you have a VM landline 150


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

Tom_F
Forum Team (Retired)
Forum Team (Retired)

Hi bittnerbarni, thanks for posting. 

 

Sorry about the connection issues you've experienced recently - thanks @Tudor for helping us identify the issue.

When checking things from here it's also clear that the hub is out of specification. So we can get an engineer visit arranged for you I will send you a PM to confirm a few details, just look out for the purple envelope and get back to me when you can.

 

Tom

Thanks Tudor and Tom!

Sent you the details.

Thanks,

Barney

Tom_F
Forum Team (Retired)
Forum Team (Retired)

Thanks for getting back to me @bittnerbarni - I've booked the visit now and you will find confirmation via your online account (virg.in/myVM) - you can also reschedule from there if needed.

 

Please keep us posted with how you get on, or let us know if we can help with anything else.

 

Tom 

Tom_F
Forum Team (Retired)
Forum Team (Retired)

Thanks for keeping me updated on this @bittnerbarni really glad to hear things have improved.

 

If you encounter any more problems or there's anything else we can help with please don't hesitate to give us another shout.

 

Tom