Menu
Reply
  • 155
  • 1
  • 25
HUGH_EFFO
Up to speed
125 Views
Message 1 of 4
Flag for a moderator

T3 timeouts again

Hi

I noticed this week i've has a lot of small disconnections again.

When I check the log, i've had 19 T3 timeouts, and my upstream power on US-4 has jumped up again.

US-4 seems to fluctuate between 46-51dBmV, and when it gets high, this seems to be when i get the issues.  The other channel (US-1) seems stable at around 47dBmV.  The downstream power levels seem ok, and I think my area is still suffering from high usage, which is effecting the speed during the evening.  (This has being going on for over a year now).

Is it worth getting an Engineer over ?

I can live with the slow speeds during the evening, but it's the disconnects that are causing me issues.

Ive included the upstream levels and the latest log files.

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

Channel Type2.0N/AN/A2.0
Channel ID2N/AN/A1
Frequency (Hz)39400000N/AN/A46200000
Ranging StatusSuccessN/AN/ASuccess
Modulation64QAMN/AN/A64QAM
Symbol Rate (Sym/sec)5120000N/AN/A5120000
Mini-Slot Size4N/AN/A4
Power Level (dBmV)47.75N/AN/A50.75
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts16003
T4 Timeouts0000

 

Network Log

Network Log
First TimeLast TimePriorityError NumberDescription
24/11/2016 13:44:49 GMT24/11/2016 13:44:49 GMTCritical (3)82000200No Ranging Response received - T3 time-out
23/11/2016 21:50:08 GMT23/11/2016 21:50:08 GMTError (4)68010400DHCP REBIND WARNING - Field invalid in response
23/11/2016 21:49:30 GMT23/11/2016 21:49:30 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 21:48:55 GMT23/11/2016 21:48:55 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 21:47:44 GMT23/11/2016 21:47:44 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 21:45:22 GMT23/11/2016 21:45:22 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 21:40:40 GMT23/11/2016 21:40:40 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 21:31:12 GMT23/11/2016 21:31:12 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 21:12:18 GMT23/11/2016 21:12:18 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 20:34:30 GMT23/11/2016 20:34:30 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 19:18:54 GMT23/11/2016 19:18:54 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 16:47:43 GMT23/11/2016 16:47:43 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 11:45:20 GMT23/11/2016 11:45:20 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
23/11/2016 01:40:35 GMT23/11/2016 01:40:35 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
22/11/2016 17:01:16 GMT22/11/2016 17:01:16 GMTCritical (3)82000200No Ranging Response received - T3 time-out
22/11/2016 09:58:22 GMT22/11/2016 09:58:22 GMTCritical (3)82000200No Ranging Response received - T3 time-out
20/11/2016 20:48:04 GMT20/11/2016 20:48:04 GMTCritical (3)82000200No Ranging Response received - T3 time-out
20/11/2016 15:00:39 GMT20/11/2016 15:00:39 GMTCritical (3)82000200No Ranging Response received - T3 time-out
20/11/2016 14:05:16 GMT20/11/2016 14:05:16 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/11/2016 23:45:41 GMT19/11/2016 23:45:41 GMTError (4)68010400DHCP REBIND WARNING - Field invalid in response
 

 

I am not a white Hat Hacker, nor a Black Hat Hacker, more 50 shades of Grey
0 Kudos
Reply
  • 155
  • 1
  • 25
HUGH_EFFO
Up to speed
99 Views
Message 2 of 4
Flag for a moderator

Re: T3 timeouts again

Update

upstream power seems to have dropped again, but still getting lots of mini disconnects.  Had 30 T3 errors since last time.

 

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

Channel Type2.0N/AN/A2.0
Channel ID2N/AN/A4
Frequency (Hz)39400000N/AN/A25800000
Ranging StatusSuccessN/AN/ASuccess
Modulation64QAMN/AN/A64QAM
Symbol Rate (Sym/sec)5120000N/AN/A5120000
Mini-Slot Size4N/AN/A4
Power Level (dBmV)46.75N/AN/A45.50
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts00030
T4 Timeouts0000

 

Network Log
First TimeLast TimePriorityError NumberDescription
28/11/2016 10:32:46 GMT28/11/2016 10:32:46 GMTCritical (3)82000200No Ranging Response received - T3 time-out
28/11/2016 04:52:55 GMT28/11/2016 04:52:55 GMTWarning (5)66050206TEK Invalid - Invalid Key Sequence Number
26/11/2016 10:13:31 GMT26/11/2016 10:13:31 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:58:56 GMT26/11/2016 06:58:56 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:58:55 GMT26/11/2016 06:58:55 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:10:11 GMT26/11/2016 06:10:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:10:10 GMT26/11/2016 06:10:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:10:08 GMT26/11/2016 06:10:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:09:19 GMT26/11/2016 06:09:19 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:09:18 GMT26/11/2016 06:09:18 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 06:09:17 GMT26/11/2016 06:09:17 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 05:14:35 GMT26/11/2016 05:14:35 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 00:55:48 GMT26/11/2016 00:55:48 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 00:55:47 GMT26/11/2016 00:55:47 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 00:55:46 GMT26/11/2016 00:55:46 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/11/2016 00:55:44 GMT26/11/2016 00:55:44 GMTCritical (3)82000200No Ranging Response received - T3 time-out
25/11/2016 23:38:47 GMT25/11/2016 23:38:47 GMTCritical (3)82000200No Ranging Response received - T3 time-out
25/11/2016 21:56:40 GMT25/11/2016 21:56:40 GMTCritical (3)82000200No Ranging Response received - T3 time-out
25/11/2016 20:14:51 GMT25/11/2016 20:14:51 GMTCritical (3)82000200No Ranging Response received - T3 time-out
25/11/2016 16:55:25 GMT25/11/2016 16:55:25 GMTCritical (3)82000200No Ranging Response received - T3 time-out
 
 
 

 

I am not a white Hat Hacker, nor a Black Hat Hacker, more 50 shades of Grey
0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
76 Views
Message 3 of 4
Flag for a moderator

Re: T3 timeouts again

Hi HUGH_EFFO, 

Thanks for getting in touch to let us know about your issues with your connection dropping out, I apologise or any troubles incurred.

I have tested things from here and I can see that your Hubs logs show a lot of T3 time outs inside, this will explain your issues. I would like to arrange for this to investigated further by one of our engineers for you.

I will send you a PM (purple envelope at the top) detailing what's required to proceed with making the booking. Please respond to me there and I'll get this sorted for you.

Take care, 

Thanks, 

Adam.


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


0 Kudos
Reply
  • 155
  • 1
  • 25
HUGH_EFFO
Up to speed
60 Views
Message 4 of 4
Flag for a moderator

Re: T3 timeouts again

Hi

Engineer came round last week and changed a couple of the splitters as he said they were causing a noise on the line.

Things have not improved as i am still getting a lot of mini disconnects, and timeouts. 

Here is the latest snapshot of my router status. I reset the logs after the visit.  As you can see the power level on US-4 has jumped up again.

Upstream
Upstream   US-1 US-2 US-3 US-4
Channel Type2.0N/AN/A2.0
Channel ID2N/AN/A1
Frequency (Hz)39400000N/AN/A46200000
Ranging StatusSuccessN/AN/ASuccess
Modulation64QAMN/AN/A64QAM
Symbol Rate (Sym/sec)5120000N/AN/A5120000
Mini-Slot Size4N/AN/A4
Power Level (dBmV)47.00N/AN/A50.00
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts26001
T4 Timeouts0000
 
 

Network Log

Network Log
First TimeLast TimePriorityError NumberDescription
20/12/2016 10:32:44 GMT20/12/2016 10:32:44 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
20/12/2016 09:33:42 GMT20/12/2016 09:33:42 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
20/12/2016 07:35:38 GMT20/12/2016 07:35:38 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
20/12/2016 03:39:31 GMT20/12/2016 03:39:31 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
19/12/2016 19:47:19 GMT19/12/2016 19:47:19 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
19/12/2016 07:49:21 GMT19/12/2016 07:49:21 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:20 GMT19/12/2016 07:49:20 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:18 GMT19/12/2016 07:49:18 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:17 GMT19/12/2016 07:49:17 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:16 GMT19/12/2016 07:49:16 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:15 GMT19/12/2016 07:49:15 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:13 GMT19/12/2016 07:49:13 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:12 GMT19/12/2016 07:49:12 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:11 GMT19/12/2016 07:49:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:10 GMT19/12/2016 07:49:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:09 GMT19/12/2016 07:49:09 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 07:49:07 GMT19/12/2016 07:49:07 GMTCritical (3)82000200No Ranging Response received - T3 time-out
19/12/2016 04:02:51 GMT19/12/2016 04:02:51 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
18/12/2016 20:19:16 GMT18/12/2016 20:19:16 GMTCritical (3)82000200No Ranging Response received - T3 time-out
18/12/2016 20:19:15 GMT18/12/2016 20:19:15 GMTCritical (3)82000200No Ranging Response received - T3 time-out

 

Downstream
Downstream   DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz)219000000227000000235000000243000000251000000259000000267000000275000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID7891011121314
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)-5.13-4.99-5.02-5.07-5.16-4.93-4.53-4.14
RxMER (dB)34.2134.6334.3534.6334.7734.6334.7735.08
Pre RS Errors3897832157681595449514842884565473411113625
Post RS Errors278328292293310332311288
 
 

 

 

I am not a white Hat Hacker, nor a Black Hat Hacker, more 50 shades of Grey
0 Kudos
Reply