Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Why do I have so many T3 timeouts?

Go to solution
meeeeehmet
Tuning in

on ‎15-08-2020 15:30

Hi

I'm checking my Superhub 2ac network log and I have a lot of T3 timeouts as shown below. Frequently, my Superhub seems to be restarting by itself and has been dropping connections too. Any reasons as to why this may be happening?

Network Log

First TimeLast TimePriorityError NumberDescription
15/08/2020 14:07:00 GMT15/08/2020 14:07:00 GMTWarning (5)66050310Auth Success - Web login successful.
15/08/2020 14:06:54 GMT15/08/2020 14:06:54 GMTError (4)68010302DHCP WAN IP - **.**.***.***
15/08/2020 14:05:51 GMT15/08/2020 14:05:51 GMTError (4)68000407TOD established
Time Not EstablishedTime Not EstablishedCritical (3)82000200No Ranging Response received - T3 time-out
Time Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully
15/08/2020 13:52:42 GMT15/08/2020 13:52:42 GMTWarning (5)66050310Auth Success - Web login successful.
14/08/2020 17:10:26 GMT14/08/2020 17:10:26 GMTWarning (5)66050310Auth Success - Web login successful.
13/08/2020 01:18:34 GMT13/08/2020 01:18:34 GMTError (4)68010302DHCP WAN IP - **.***.***.***
13/08/2020 01:17:48 GMT13/08/2020 01:17:48 GMTError (4)68000407TOD established
13/08/2020 01:17:38 GMT13/08/2020 01:17:38 GMTNotice (6)84000510Downstream Locked Successfully
13/08/2020 01:17:32 GMT13/08/2020 01:17:32 GMTCritical (3)82000200No Ranging Response received - T3 time-out
13/08/2020 01:17:32 GMT13/08/2020 01:17:32 GMTCritical (3)82000200No Ranging Response received - T3 time-out
13/08/2020 01:17:32 GMT13/08/2020 01:17:32 GMTCritical (3)82000200No Ranging Response received - T3 time-out
13/08/2020 01:17:32 GMT13/08/2020 01:17:32 GMTCritical (3)82000200No Ranging Response received - T3 time-out
13/08/2020 01:17:31 GMT13/08/2020 01:17:31 GMTCritical (3)82000700Unicast Ranging Received Abort Response - initializing MAC
13/08/2020 01:17:31 GMT13/08/2020 01:17:31 GMTCritical (3)82000700Unicast Ranging Received Abort Response - initializing MAC
13/08/2020 01:17:31 GMT13/08/2020 01:17:31 GMTCritical (3)82000700Unicast Ranging Received Abort Response - initializing MAC
13/08/2020 01:17:31 GMT13/08/2020 01:17:31 GMTCritical (3)82000700Unicast Ranging Received Abort Response - initializing MAC
13/08/2020 01:17:13 GMT13/08/2020 01:17:13 GMTCritical (3)82000200No Ranging Response received - T3 time-out
13/08/2020 01:16:49 GMT13/08/2020 01:16:49 GMTCritical (3)82000200No Ranging Response received - T3 time-out

 

Downstream  DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)139000000147000000155000000163000000171000000179000000187000000195000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID12345678
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17		I=12
J=17		I=12
J=17		I=12
J=17		I=12
J=17		I=12
J=17		I=12
J=17		I=12
J=17
Power Level (dBmV)-0.32-0.76-1.18-1.79-2.13-2.51-2.90-3.00
RxMER (dB)37.0937.3637.6437.9438.2637.9437.9437.94
Pre RS Errors449387292301292866302299
Post RS Errors287291279297289866302299

 

Upstream  US-1 US-2 US-3 US-4

Channel Type2.02.02.02.0
Channel ID8657
Frequency (Hz)39400000537000006030000046200000
Ranging StatusSuccessSuccessSuccessSuccess
Modulation32QAM64QAM64QAM64QAM
Symbol Rate (Sym/sec)5120000512000051200005120000
Mini-Slot Size2222
Power Level (dBmV)51.0051.0051.0051.00
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts1000
T4 Timeouts0000

 

Upstream Burst  Req(1) Init Maint(3) Per Maint(4) Adv Short(9) Adv Long(10) Adv UGS(11)

Modulation Type16QAMQPSK16QAM32QAM32QAM16QAM
Differential EncodingOFFOFFOFFOFFOFFOFF
Preamble Length56640384104104104
Preamble Value Offset65200716716716
FEC Error Correction (T)0558135
FEC Codeword Information Bytes (K)16343411422086
Maximum Burst Size0004255255
Guard Time Size84848888
Last Codeword LengthFixedFixedFixedShortenedShortenedShortened
Scrambler On/OffONONONONONON
0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions

Go to solution
Anonymous
Not applicable

‎15-08-2020 15:39 - edited ‎15-08-2020 15:40

Because your upstream power levels are too high and one of your upstream channels is out of spec (32 qam, when it should be 64 qam).

See where this Helpful Answer was posted

35 REPLIES 35

Go to solution
Anonymous
Not applicable

‎15-08-2020 15:39 - edited ‎15-08-2020 15:40

Because your upstream power levels are too high and one of your upstream channels is out of spec (32 qam, when it should be 64 qam).

Go to solution
meeeeehmet
Tuning in
In response to Anonymous

on ‎15-08-2020 16:26

What do I need to do to fix this?

0 Kudos

Go to solution
Anonymous
Not applicable
In response to meeeeehmet

on ‎15-08-2020 16:26

Arrange an engineer visit with VM.

0 Kudos

Go to solution
meeeeehmet
Tuning in
In response to Anonymous

on ‎15-08-2020 16:40

Thank you!!  🙂

0 Kudos

Go to solution
meeeeehmet
Tuning in
In response to Anonymous

on ‎17-08-2020 16:30

I called up Virgin today and they ran some 'tests' and said my hub is working properly. I was forwarded to another person who then sent out a new hub for me. Will this resolve the issues?

0 Kudos

Go to solution
MikeRobbo
Alessandro Volta
In response to meeeeehmet

on ‎17-08-2020 16:39

I doubt a replacement Hub will fix your problem.

It is a cheap way of solving your problem for a few days.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.

Go to solution
meeeeehmet
Tuning in
In response to MikeRobbo

on ‎17-08-2020 16:42

I, too, doubt it will fix my connection problems. I game quite a lot and I've heard the Puma 7 chipset flaw with the hub 3. I hope I wont get heavily impacted by the high latency, or that virgin has fixed the issue.

If the issue resolves after a few months of my hub being fitted in, I'll definitely be sure to call them back again and persuade them to send out an engineer.

0 Kudos

Go to solution
Chris_W1
Forum Team
Forum Team
In response to meeeeehmet

on ‎24-08-2020 16:45

Hi meeeeehmet, thanks for contacting us, can you confirm if the hub has now arrived and if there is any change with the connection? ^Chris 

0 Kudos

Go to solution
meeeeehmet
Tuning in
In response to Chris_W1

on ‎26-08-2020 19:41

Hi Chris,

I have been using the hub for more than a week now and I still have no change with the connection. If anything, the connection has gotten much worse.

The old superhub had a stable network connection all the way upstairs to my living room but now on the new hub the connection disconnects as soon as I go up the stairs.

On top of that, I've been getting more T3 and T4 time-outs. Take a look for yourself:

Network Log

Time Priority Description

26/08/2020 18:30:32noticeLAN login Success;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 16:41:54Warning!RCS Partial Service;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 02:37:24ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 02:07:37criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 02:04:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 02:03:49criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 01:59:48criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 01:58:53Warning!Lost MDD Timeout;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 01:58:48criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 01:58:47Warning!RCS Partial Service;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/08/2020 01:58:47criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2020 17:26:6ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2020 13:32:23Warning!RCS Partial Service;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2020 10:43:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2020 07:08:0ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/08/2020 13:25:39Warning!RCS Partial Service;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/08/2020 02:56:23noticeLAN login Success;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/08/2020 18:01:54Warning!RCS Partial Service;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/08/2020 15:53:7noticeLAN login Success;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/08/2020 12:09:56Warning!RCS Partial Service;CM-MAC=**:**:**::****:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Top