Menu
Reply
  • 3
  • 0
  • 0
Danko
Joining in
207 Views
Message 1 of 5
Flag for a moderator

Hub 3.0 restarts at random, unreliable ping and packetloss.

Hi,

We experience regular issues with the Hub 3.0 restarting itself. Outside of that, we also seem to have issues with minor drop outs, high ping and sometimes packet loss - especially noticable while gaming.

It seems to mostly log

No Ranging Response received - T3 time-out

and I think this is causing the issue.

Network Log:

11/08/2019 18:26:5criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2019 00:38:28Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2019 07:27:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2019 18:12:30Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/08/2019 12:32:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/08/2019 16:52:58Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/08/2019 21:06:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/08/2019 19:28:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/08/2019 09:16:1ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/08/2019 11:04:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/08/2019 20:53:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/08/2019 21:06:8ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/08/2019 22:39:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/08/2019 03:01:13ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/08/2019 08:56:19ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/08/2019 08:56:19noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/08/2019 22:04:52Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/08/2019 13:27:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2019 12:14:25Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2019 13:57:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream:

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

14030000000.736256 qam28
2187000000536256 qam7
31950000004.536256 qam8
42030000003.936256 qam9
52110000003.536256 qam10
62190000003.436256 qam11
7227000000336256 qam12
82350000002.736256 qam13
92430000002.436256 qam14
102510000002.236256 qam15
112590000001.936256 qam16
122670000002.236256 qam17
132750000002.236256 qam18
142830000002.937256 qam19
152910000003.437256 qam20
162990000003.537256 qam21
173070000003.537256 qam22
183150000003.537256 qam23
19323000000337256 qam24
203790000001.937256 qam25
213870000001.537256 qam26
22395000000136256 qam27
234110000000.736256 qam29
244190000000.736256 qam30

 

Upstream:

1394000004.025512016 qam2
2257999593.825512016 qam4
3325999933.875512016 qam3
4461999794.025512016 qam1
0 Kudos
Reply
  • 20
  • 0
  • 9
kloopk
On our wavelength
187 Views
Message 2 of 5
Flag for a moderator

Re: Hub 3.0 restarts at random, unreliable ping and packetloss.

I found setting up www.thinkbroadband.com to monitor the connection helped me in resolving my issues and helped the Agents/Superusers on here assist me.

its worth doing, i popped mine in the sig

0 Kudos
Reply
  • 3
  • 0
  • 0
Danko
Joining in
167 Views
Message 3 of 5
Flag for a moderator

Re: Hub 3.0 restarts at random, unreliable ping and packetloss.

I think I will try run it in modem mode with a new router. I doubt this will fix the issue but it should at least improve the wifi.

0 Kudos
Reply
  • 3
  • 0
  • 0
Danko
Joining in
137 Views
Message 4 of 5
Flag for a moderator

Re: Hub 3.0 restarts at random, unreliable ping and packetloss.

I have since installed an TP-LINK Archer VR900 and it has improved the WiFi but the superhub will still randomly stop working and I will have to restart it or wait for it to come back online. Over the past week, it's probably gone off around 3 or 4 times for no reason what so ever. Yes, the superhub is running in modem-only mode.

0 Kudos
Reply
  • 4.61K
  • 311
  • 770
Roger_Gooner
Superstar
131 Views
Message 5 of 5
Flag for a moderator

Re: Hub 3.0 restarts at random, unreliable ping and packetloss.

The router won't help the connection dropouts. Call 08005610061 to find out if there is a service fault, if there isn't you need a technician to come round. It's not good that no forum team member has been along in 16 days to assist.

--
Hub 3.0, TP-Link Archer C8, TP-Link TL-SG1008D 8-port gigabit switch, V6
My Broadband Ping - Roger's VM Broadband Connection