Menu
Reply
  • 393
  • 1
  • 3
madmanx
On our wavelength
154 Views
Message 1 of 4
Flag for a moderator

Daily t3 timeout

Hi everyday lately I'm getting a t3 timeout, only 1 each day, is that something to be concerned about? what causes them? I thought they are to do with the upstream power levels being too high but mine are at 47? Could it be a network problem? Or hub? I have also noticed my downstream snr has slightly dropped from 37.97 to 37.09 and 36.84 on one channel? Any ideas if I have a problem? 

Upstream
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)47.75N/AN/A47.00
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts4000
T4 Timeouts0000
 
0 Kudos
Reply
  • 393
  • 1
  • 3
madmanx
On our wavelength
153 Views
Message 2 of 4
Flag for a moderator

Re: Daily t3 timeout

Downstream
Downstream   DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz)266750000274750000282750000290750000298750000306750000314750000322750000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID910111213141516
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.074.994.985.004.924.764.444.15
RxMER (dB)36.8437.0937.0937.0937.6437.0937.0937.09
Pre RS Errors1748051169027195745910341051437492
Post RS Errors00000000
 
0 Kudos
Reply
  • 393
  • 1
  • 3
madmanx
On our wavelength
151 Views
Message 3 of 4
Flag for a moderator

Re: Daily t3 timeout

Network Log
Network Log
First TimeLast TimePriorityError NumberDescription
01/03/2017 13:18:47 GMT01/03/2017 13:18:47 GMTCritical (3)82000200No Ranging Response received - T3 time-out
28/02/2017 15:16:49 GMT28/02/2017 15:16:49 GMTCritical (3)82000200No Ranging Response received - T3 time-out
27/02/2017 17:49:54 GMT27/02/2017 17:49:54 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/02/2017 20:30:08 GMT26/02/2017 20:30:08 GMTError (4)68010302DHCP WAN IP - xxxxxxxxx
26/02/2017 20:29:36 GMT26/02/2017 20:29:36 GMTError (4)68000407TOD established
26/02/2017 20:29:27 GMT26/02/2017 20:29:27 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/02/2017 20:29:22 GMT26/02/2017 20:29:22 GMTNotice (6)84000510Downstream Locked Successfully
26/02/2017 20:28:43 GMT26/02/2017 20:28:43 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
26/02/2017 18:40:40 GMT26/02/2017 18:40:40 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
26/02/2017 17:17:12 GMT26/02/2017 17:17:12 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/02/2017 15:04:33 GMT26/02/2017 15:04:33 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
26/02/2017 07:52:20 GMT26/02/2017 07:52:20 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
25/02/2017 17:27:55 GMT25/02/2017 17:27:55 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
 
 
0 Kudos
Reply
  • 10K
  • 294
  • 625
Forum Team
Forum Team
134 Views
Message 4 of 4
Flag for a moderator

Re: Daily t3 timeout

Hey madmanx,

Thanks for posting Smiley Happy

I appreciate you taking the time to post your readings, it's much appreciated. What's strange is when I look from our end, it looks to me like your Superhub has been online for 37 days and has only accumulated one T3 time-out in this time. Your power and SNR levels are looking good too. When did you last reboot? My tools might be misreporting so please get back to me so I can investigate further.

Take care.

Heather_J

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


0 Kudos
Reply