T4 Timeout
 

Hi All. Having a few issues with my connection over the past few days and wondering if anyone may know why.

When the Super Hub boots it seems to lock on to the network fine, however there is no Internet connectivity. Strangely, I have noticed that the Super Hub GUI is only available for a few minutes at start up before it becomes unusable.

When connected all power levels seem fine to me:

Downstream:

DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 299000000 267000000 275000000 283000000 291000000 307000000 315000000 323000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Locked Locked Locked Locked
Channel ID 9 5 6 7 8 10 11 12
Modulation 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM
Symbol Rate (Msym/sec) 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000
Interleave Depth 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 I=12
J=17
Power Level (dBmV) 3.19 3.28 3.50 3.37 3.33 3.43 3.50 3.73
RxMER (dB) 37.36 36.84 36.84 37.09 37.64 37.36 37.94 37.94
Pre RS Errors
314 425 286 301 316 280 290 353
Post RS Errors
290 284 281 296 312 269 290 353

Upstream:

US-1 US-2 US-3 US-4
Channel Type 2.0 N/A N/A 2.0
Channel ID 3 N/A N/A 1
Frequency (Hz) 32600000 N/A N/A 46200000
Ranging Status Success N/A N/A Success
Modulation 16QAM N/A N/A 16QAM
Symbol Rate (Sym/sec) 5120000 N/A N/A 5120000
Mini-Slot Size 4 N/A N/A 4
Power Level (dBmV) 38.00 N/A N/A 38.50
T1 Timeouts 2 2 2 2
T2 Timeouts 0 0 0 0
T3 Timeouts 0 0 0 0
T4 Timeouts 0 0 0 0

I have noticed on the operations log a lot of T4 Timeouts, although I am not sure what this means.

5/01/2016 20:11:04 GMT 15/01/2016 20:11:04 GMT Error (4) 68000407 TOD established
15/01/2016 20:10:55 GMT 15/01/2016 20:10:55 GMT Notice (6) 84000510 Downstream Locked Successfully
15/01/2016 20:10:47 GMT 15/01/2016 20:10:47 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:10:25 GMT 15/01/2016 20:10:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:09:25 GMT 15/01/2016 20:09:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:08:25 GMT 15/01/2016 20:08:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:07:25 GMT 15/01/2016 20:07:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:06:25 GMT 15/01/2016 20:06:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:05:25 GMT 15/01/2016 20:05:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:04:25 GMT 15/01/2016 20:04:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:03:25 GMT 15/01/2016 20:03:25 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:02:40 GMT 15/01/2016 20:02:40 GMT Error (4) 67070100 DBC-ACK not received
15/01/2016 20:02:38 GMT 15/01/2016 20:02:38 GMT Warning (5) 85010200 TCS Partial Service
15/01/2016 20:01:55 GMT 15/01/2016 20:01:55 GMT Error (4) 68000407 TOD established
15/01/2016 20:01:43 GMT 15/01/2016 20:01:43 GMT Notice (6) 84000510 Downstream Locked Successfully
15/01/2016 20:01:34 GMT 15/01/2016 20:01:34 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:01:11 GMT 15/01/2016 20:01:11 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 20:00:11 GMT 15/01/2016 20:00:11 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 19:59:11 GMT 15/01/2016 19:59:11 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
15/01/2016 19:58:11 GMT 15/01/2016 19:58:11 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

The error appears to occur over and over until eventually the hub appears to work fine!

Anyone know what could be causing this?

Thanks :)

Re: T4 Timeout
 

This is exactly what I get, about an hour of unuseable connection on boot.

VM says it's to do with the upstream being noisy and they have been investigating it since I reported it in September 2015.

If you have a thinkbroadband monitor it may look like mine... the bit from 11am to 12 am.

[img]Download Failed (1)[/img]

http://www.thinkbroadband.com/ping/monitors.html

---------- Post added at 11:04 ---------- Previous post was at 11:01 ----------

Here's my thread on the problem, have a look and see if it rings any bells with you. If it does please add a comment and hopefully it might trigger a reaction from VM...


http://community.virginmedia.com/t5/...2917052#M47374

Re: T4 Timeout
 

I just replied to your thread over at Virgin Media funnily enough! Haven't had a TBB Graph for years, I have just set one up to see.