Menu
Reply
Highlighted
  • 43
  • 0
  • 0
Joining in
246 Views
Message 1 of 5
Flag for a moderator

No ranging response - T3 timeout

I am having intermittent service drop-outs that are only solved by restarting the hub. 

I am posting router stats below in the hope somebody can suggest a solution.  The connection is fine at the moment though, so am not sure whether the downstream and upstream stats are helpful or if I need to copy and post those while the service is not working?

By way of background, I've been on Virgin for years with the same Superhub in the same place connected to the same wired and wireless devices for a very long time, so there is nothing new in the wired connection to the outside world or to devices in the house that might have caused this.

0 Kudos
Reply
Highlighted
  • 43
  • 0
  • 0
Joining in
245 Views
Message 2 of 5
Flag for a moderator

Re: No ranging response - T3 timeout

Network Log

Time

Priority

Description

22/03/2020 20:18:55

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

22/03/2020 20:14:3

critical

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

22/03/2020 20:00:9

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

22/03/2020 19:59:5

critical

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

22/03/2020 19:16:22

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

22/03/2020 05:22:48

critical

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

21/03/2020 18:28:6

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

20/03/2020 19:27:38

critical

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

18/03/2020 21:34:37

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

15/03/2020 15:36:20

critical

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

15/03/2020 04:27:27

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

15/03/2020 02:53:3

notice

DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsl10016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

15/03/2020 02:53:3

Error

DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

14/03/2020 10:39:46

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

12/03/2020 19:10:25

critical

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

11/03/2020 23:01:27

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

10/03/2020 04:53:22

critical

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

09/03/2020 01:31:53

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

09/03/2020 01:27:15

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

08/03/2020 23:39:17

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply
Highlighted
  • 43
  • 0
  • 0
Joining in
241 Views
Message 3 of 5
Flag for a moderator

Re: No ranging response - T3 timeout

Downstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

SNR (dB)

Modulation

Channel ID

1

322750000

3.4

38

256 qam

24

2

138750000

5.5

38

256 qam

1

3

146750000

5.5

38

256 qam

2

4

154750000

5.6

38

256 qam

3

5

162750000

5.5

40

256 qam

4

6

170750000

5.4

40

256 qam

5

7

178750000

5.1

38

256 qam

6

8

186750000

5

38

256 qam

7

9

194750000

4.8

40

256 qam

8

10

202750000

4.5

38

256 qam

9

11

210750000

4.3

38

256 qam

10

12

218750000

4.1

40

256 qam

11

13

226750000

4

38

256 qam

12

14

234750000

3.7

38

256 qam

13

15

242750000

3.5

38

256 qam

14

16

250750000

3.4

38

256 qam

15

17

258750000

3.2

38

256 qam

16

18

266750000

3.2

38

256 qam

17

19

274750000

3

38

256 qam

18

20

282750000

3

38

256 qam

19

21

290750000

3

38

256 qam

20

22

298750000

3.4

38

256 qam

21

23

306750000

3.4

38

256 qam

22

24

314750000

3.5

38

256 qam

23

 

Downstream bonded channels

Channel

Locked Status

RxMER (dB)

Pre RS Errors

Post RS Errors

1

Locked

38.9

17

0

2

Locked

38.9

12

0

3

Locked

38.9

21

0

4

Locked

38.9

24

0

5

Locked

40.3

8

0

6

Locked

40.3

10

0

7

Locked

38.9

8

0

8

Locked

38.9

3

0

9

Locked

40.3

9

0

10

Locked

38.9

8

0

11

Locked

38.9

10

0

12

Locked

40.3

7

0

13

Locked

38.6

6

0

14

Locked

38.9

10

0

15

Locked

38.9

7

0

16

Locked

38.9

10

0

17

Locked

38.9

8

0

18

Locked

38.6

3

0

19

Locked

38.9

6

0

20

Locked

38.9

7

0

21

Locked

38.6

13

0

22

Locked

38.6

7

0

23

Locked

38.9

7

0

24

Locked

38.9

20

0

 

Upstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

Symbol Rate (ksps)

Modulation

Channel ID

1

46200000

4.275

5120

64 qam

3

2

39400000

4.225

5120

64 qam

4

3

53699957

4.275

5120

64 qam

2

4

60299983

4.425

5120

64 qam

1




Upstream bonded channels

Channel

Channel Type

T1 Timeouts

T2 Timeouts

T3 Timeouts

T4 Timeouts

1

ATDMA

0

0

0

0

2

ATDMA

0

0

0

0

3

ATDMA

0

0

0

0

4

ATDMA

0

0

0

0

 

0 Kudos
Reply
Highlighted
  • 6.43K
  • 476
  • 844
Hero
224 Views
Message 4 of 5
Flag for a moderator

Re: No ranging response - T3 timeout

There doesn't seem to be anything untoward in the data.

Set up a Broadband Quality Monitor (BQM) at thinkbroadband.com - this will give you an insight into what is happening with the signal at the Hub, it will take a few hours to get any kind of trend showing.

Post a link to your BQM on here.

Instructions for posting BQM Link

Under your BQM graph are two links in red.

Click the lower link (Share Live Graph) then click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see.

On here click the Link icon (2 links chain to the left of the camera icon)

 In the URL box paste the link you copied and then click OK.

***********************************************************************************************************************************

Mike Robinson
Aircraft Engineer & Computer Based Training and Learning Designer for many of the world's Military Arms.


My Broadband Ping - 26_Aug_2020
0 Kudos
Reply
Highlighted
  • 43
  • 0
  • 0
Joining in
206 Views
Message 5 of 5
Flag for a moderator

Re: No ranging response - T3 timeout

Thanks. Spoke to VM this evening and they said there has been a usage problem in the local area for the past 2-3 weeks which was rectified this morning so hopefully it will all return to normal now. 

0 Kudos
Reply