Menu
Reply
  • 34
  • 0
  • 1
Jinxey
On our wavelength
3,996 Views
Message 1 of 14
Flag for a moderator

T4 Timeout

I have been having a few issues with my Internet connection recently.

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.

Smiley Sad Thanks.

0 Kudos
Reply
  • 9.37K
  • 362
  • 2.31K
Superuser
Superuser
3,975 Views
Message 2 of 14
Flag for a moderator

Re: T4 Timeout

http://volpefirm.com/docsis_timout_descriptions/

Basically there was some disruption to the network for around 12 minutes, during which time your hub tried to reconnect over and over again until it could get a connection.

The hub GUI will be unusable during periods where the modem is trying to reconnect to the network.

Setup a Thinkbroadband BQM graph to monitor your connection: http://www.thinkbroadband.com/ping

Follow the instructions about enabling the Ping option on your router. Then post a link to the live graph.

 

  • 13.02K
  • 371
  • 1.06K
Moderator
Moderator
3,944 Views
Message 3 of 14
Flag for a moderator

Re: T4 Timeout

Hi Jinxey,

 

Good to hear from you, though disappointing that your connection has been playing upSmiley Sad

 

Muddy is spot on with respect to the time-outs and GUI not being available. I've also run a few checks on your service from this end and both your SuperHub and local network segment are reporting back in pretty good shape, bar a little peak time build up in traffic.

 

What kind of problems are you experiencing, if issues continue drop us a few more details and we'll gladly try and assist further.

 

Cheers

 

 

 

Ralph_R
Forum Moderator

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


  • 34
  • 0
  • 1
Jinxey
On our wavelength
3,928 Views
Message 4 of 14
Flag for a moderator

Re: T4 Timeout

Hi Ralph,

Thanks for the reply. The main issue was that the hub was taking in excess of 30 minutes to connect when booting after being turned off. It had been happening on multiple occasions leading me to think there might be a fault. Having rebooted the hub twice this week this seems to have settled down and the hub is behaving as normal now and connects pretty quickly with no T4's reported. It looks like whatever was causing it has been resolved.

Thanks for checking over the connection, it is much appreciated. I think we can put this to one side for now. Will report back if the issues reappear! Smiley Happy

0 Kudos
Reply
  • 9.37K
  • 362
  • 2.31K
Superuser
Superuser
3,908 Views
Message 5 of 14
Flag for a moderator

Re: T4 Timeout


Jinxey wrote:

 

The main issue was that the hub was taking in excess of 30 minutes to connect when booting after being turned off. It had been happening on multiple occasions leading me to think there might be a fault.

I've seen this same exact problem a few times in the last couple of months (and I've not been looking at many posts). 

Having rebooted the hub twice this week this seems to have settled down and the hub is behaving as normal now and connects pretty quickly with no T4's reported. It looks like whatever was causing it has been resolved.

Hmm maybe. When I see T4's only during peak time I expect it to be due to the "little peak time build up in traffic".

Thanks for checking over the connection, it is much appreciated. I think we can put this to one side for now. Will report back if the issues reappear! Smiley Happy


If it happens again I would just advise rebooting outside of peak time to avoid the issue, or don't reboot. I never reboot my hub 3 or 2ac (the only one that needed rebooting was the old Superhub 1 when i had it enabled). 

0 Kudos
Reply
  • 34
  • 0
  • 1
Jinxey
On our wavelength
3,883 Views
Message 6 of 14
Flag for a moderator

Re: T4 Timeout

Spoke too soon. This seems to be happening again.... Took in excess of 45 minutes for the connection to be stable enough to use the other night Smiley Sad

1/02/2016 18:28:42 GMT11/02/2016 18:28:42 GMTError (4)68000407TOD established
11/02/2016 18:28:33 GMT11/02/2016 18:28:33 GMTNotice (6)84000510Downstream Locked Successfully
11/02/2016 18:28:01 GMT11/02/2016 18:28:01 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:27:01 GMT11/02/2016 18:27:01 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:26:01 GMT11/02/2016 18:26:01 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:25:01 GMT11/02/2016 18:25:01 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:24:01 GMT11/02/2016 18:24:01 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:23:01 GMT11/02/2016 18:23:01 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:22:01 GMT11/02/2016 18:22:01 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:21:18 GMT11/02/2016 18:21:18 GMTError (4)67070100DBC-ACK not received
11/02/2016 18:21:16 GMT11/02/2016 18:21:16 GMTWarning (5)85010200TCS Partial Service
11/02/2016 18:20:31 GMT11/02/2016 18:20:31 GMTError (4)68000407TOD established
11/02/2016 18:20:19 GMT11/02/2016 18:20:19 GMTNotice (6)84000510Downstream Locked Successfully
11/02/2016 18:19:45 GMT11/02/2016 18:19:45 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:18:45 GMT11/02/2016 18:18:45 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:17:45 GMT11/02/2016 18:17:45 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:16:45 GMT11/02/2016 18:16:45 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:15:45 GMT11/02/2016 18:15:45 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:14:45 GMT11/02/2016 18:14:45 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
11/02/2016 18:13:45 GMT11/02/2016 18:13:45 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
0 Kudos
Reply
  • 34
  • 0
  • 1
Jinxey
On our wavelength
3,860 Views
Message 7 of 14
Flag for a moderator

Re: T4 Timeout

Lots of T3 Timeouts now too.... Smiley Sad

16/02/2016 09:44:18 GMT 16/02/2016 09:44:18 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:43:38 GMT 16/02/2016 09:43:38 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:42:58 GMT 16/02/2016 09:42:58 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:42:18 GMT 16/02/2016 09:42:18 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:41:58 GMT 16/02/2016 09:41:58 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:41:40 GMT 16/02/2016 09:41:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:41:38 GMT 16/02/2016 09:41:38 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:41:20 GMT 16/02/2016 09:41:20 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:41:18 GMT 16/02/2016 09:41:18 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:41:07 GMT 16/02/2016 09:41:07 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:41:00 GMT 16/02/2016 09:41:00 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:40:58 GMT 16/02/2016 09:40:58 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:40:47 GMT 16/02/2016 09:40:47 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:40:40 GMT 16/02/2016 09:40:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:40:38 GMT 16/02/2016 09:40:38 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
16/02/2016 09:40:27 GMT 16/02/2016 09:40:27 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
3,837 Views
Message 8 of 14
Flag for a moderator

Re: T4 Timeout

Hi Jinxey, 

 

Thanks for keeping us up to date on your issues, apologies for any bother.

 

I've run some checks on things from this end and I can't see any problems that would explain the time outs you mentioned, are these problems still affecting your connection?

 

If so we would need to arrange for an engineer to visit and investigate things further, it would be helpful if you could post back here to let me know.

 

I look forward to hearing from you, 

Thanks, 

Adam.


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply
  • 6
  • 0
  • 0
David_J_R
Joining in
3,811 Views
Message 9 of 14
Flag for a moderator

Re: T4 Timeout

Hi Jinxey

Just curious if this ever got sorted out as I've been experiencing a similar problem with my SH2ac since November. It sometimes loses the connection and when trying to re-establish, it take about an hour as it runs though 5 batches each of 9 off T4 timeouts. VM are still trying to work out the cause. But when it happens the course of events before connection is re-established it very predictable and it can be initiated simply by re-booting the SH2ac

David

0 Kudos
Reply
  • 13.02K
  • 371
  • 1.06K
Moderator
Moderator
3,786 Views
Message 10 of 14
Flag for a moderator

Re: T4 Timeout

Hi David,

 

Thanks for the update and all the Hub stats, very useful though disappointing to see that connection problems remain ongoing for you. 

 

The Hubs upstream power levels and downstream SNR (RxMER) are both very borderline which may be the cause of the Timeout events and connections drops if spiking further.

 

As I can't see any wider network problems to explain any fault I think the best course of action is to arrange for the area Principal Engineer to call and investigate, I'll drop you a Private Message so we can book this in.

 

Kind Regards

 

 

 

 

Ralph_R
Forum Moderator

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply