cancel
Showing results for 
Search instead for 
Did you mean: 

Why do I have so many T3 timeouts?

meeeeehmet
Tuning in

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
35 REPLIES 35

post the levels from the new hub

log into hub3 - 192.168.0.1 [or 192.168.100.1 if in modem mode] - DON'T SIGN IN, click - click router status [centre of screen] - and post the downstream and upstream figures - to see those press on the grey buttons/boxes labelled - upstream - downstream

as said above the upstream was out of spec at 51 on the old hub - or was said to be in the past - they now seem to accept 52 but generally if you dont have problem - if its the same on the hub3 - it displays as 5.1 for 51 as theres bug in the reporting software i would push for a tech to reduce them

the wifi is about the same on the hub3 but only if you set it up - split the wifi bands and turn off smart wifi

____________________

Tony.
Sacked VIP

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1227000000-1.238256 qam12
2219000000-1.238256 qam11
3235000000-1.538256 qam13
4243000000-1.538256 qam14
5251000000-1.738256 qam15
6259000000-1.938256 qam16
7267000000-238256 qam17
8275000000-2.238256 qam18
9283000000-238256 qam19
10291000000-2.538256 qam20
11299000000-2.738256 qam21
12307000000-240256 qam22
13315000000-1.740256 qam23
14323000000-1.440256 qam24
15331000000-1.540256 qam25
16339000000-0.938256 qam26
17347000000-1.238256 qam27
18355000000-1.538256 qam28
19363000000-1.240256 qam29
20371000000-1.738256 qam30
21379000000-1.738256 qam31
22387000000-1.740256 qam32
23395000000-1.940256 qam33
24403000000-1.740256 qam34



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.947363
2Locked38.93652
3Locked38.9107153
4Locked38.934536
5Locked38.64936
6Locked38.914227678737
7Locked38.66436
8Locked38.670115
9Locked38.967136
10Locked38.615039
11Locked38.689114
12Locked40.36042
13Locked40.36445
14Locked40.36046
15Locked40.35346
16Locked38.94545
17Locked38.94037
18Locked38.993119
19Locked40.32639
20Locked38.67049
21Locked38.95964
22Locked40.33866
23Locked40.94838
24Locked40.94652

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1537001435.1512064 qam6
2603002135.1512064 qam5
3394000095.1512064 qam8
4461998915.1512064 qam7

 

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

not sure whats happening on channel 6 - something very odd there and the hub change has not helped the upstream levels - not that it would be expected to other than offshore saying it would - its too high imo but you need to get VM to agree and send a tech

____________________

Tony.
Sacked VIP

I definitely agree and think that an engineer should be sent out.

I'm no expert in this stuff, I don't even know what any of these numbers and values mean lol. But I checked channel 6 again and my Pre RS Errors count is 468923251 as of 10:56PM on the 26th August. I'm pretty sure that's bad

reboot the hub - that will zero the error counts and then see what they are in a few hours and post back - make sure all the coax connections are tight

____________________

Tony.
Sacked VIP

I restarted my hub 3 at 7:21PM. The time is now 9:35PM as of copying and pasting the network log.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1227000000-138256 qam12
2219000000-138256 qam11
3235000000-1.438256 qam13
4243000000-1.438256 qam14
5251000000-1.538256 qam15
6259000000-1.538256 qam16
7267000000-1.738256 qam17
8275000000-238256 qam18
9283000000-1.938256 qam19
10291000000-2.438256 qam20
11299000000-2.538256 qam21
12307000000-1.940256 qam22
13315000000-1.540256 qam23
14323000000-1.240256 qam24
15331000000-1.538256 qam25
16339000000-0.938256 qam26
17347000000-0.940256 qam27
18355000000-1.238256 qam28
19363000000-140256 qam29
20371000000-1.538256 qam30
21379000000-1.538256 qam31
22387000000-1.440256 qam32
23395000000-1.740256 qam33
24403000000-1.540256 qam34



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.92450
2Locked38.9100
3Locked38.93950
4Locked38.9780
5Locked38.950
6Locked38.92374115570
7Locked38.980
8Locked38.900
9Locked38.900
10Locked38.6160
11Locked38.650
12Locked40.350
13Locked40.370
14Locked40.350
15Locked38.910
16Locked38.950
17Locked40.350
18Locked38.910
19Locked40.300
20Locked38.980
21Locked38.980
22Locked40.360
23Locked40.340
24Locked40.370

Anonymous
Not applicable

Upstream power levels are very high as well (Still!).

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1537001435.1512064 qam6
2603002135.1512064 qam5
3394000095.1512064 qam8
4461998915.1512064 qam7

 

-tony-
Alessandro Volta

have flagged the thread !!

____________________

Tony.
Sacked VIP

Was just looking at my network logs and thought it might be worth uploading some more info:

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1537000835.1512064 qam6
2602998705.1512064 qam5
3462002465.1512064 qam7
4394002855.1512064 qam8

 

Time Priority Description

01/01/1970 00:01:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/08/2020 23:25:5noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/08/2020 22:54:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Why do I have a T3 timeout at 01/01/1970???? lol

Anonymous
Not applicable

@meeeeehmet wrote:

Was just looking at my network logs and thought it might be worth uploading some more info:

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1537000835.1512064 qam6
2602998705.1512064 qam5
3462002465.1512064 qam7
4394002855.1512064 qam8

 

Time Priority Description

01/01/1970 00:01:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/08/2020 23:25:5noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/08/2020 22:54:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Why do I have a T3 timeout at 01/01/1970???? lol


The HUB tries to synchronize its local time with a remote process. Sometimes it can't hence the 'odd' date & time.