Menu
Reply
  • 6
  • 0
  • 0
junker404
Joining in
203 Views
Message 1 of 9
Flag for a moderator

vivid 200 super Hub 2 keeps dropping

Please Help - vivid 200 super Hub 2 keeps dropping

 

We have been with VM for 10yrs with no real problems, but getting really fed with this,

it`s been steadily getting worse over 6 months

 

The hub drops every couple of hours other times two or three drops a day

when dropped the up/down arrows on hub turn green, sometimes it reconnects its self

other times we have to reboot hub to connect. We have both wired and wireless the hub

drops everything. The speed is fast when the hub works.

 

after reading other posts I tried to find out what info to post

 

Network Log

First Time

Last Time

Priority

Error Number

Description

04/08/2017 14:26:28 GMT

04/08/2017 14:26:28 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:34 GMT

04/08/2017 14:26:34 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:33 GMT

04/08/2017 14:26:33 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:32 GMT

04/08/2017 14:26:32 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:32 GMT

04/08/2017 14:26:32 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:31 GMT

04/08/2017 14:26:31 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:31 GMT

04/08/2017 14:26:31 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:30 GMT

04/08/2017 14:26:30 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:30 GMT

04/08/2017 14:26:30 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:29 GMT

04/08/2017 14:26:29 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:28 GMT

04/08/2017 14:26:28 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:34 GMT

04/08/2017 14:26:34 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:33 GMT

04/08/2017 14:26:33 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:32 GMT

04/08/2017 14:26:32 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:32 GMT

04/08/2017 14:26:32 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:31 GMT

04/08/2017 14:26:31 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:31 GMT

04/08/2017 14:26:31 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:30 GMT

04/08/2017 14:26:30 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:30 GMT

04/08/2017 14:26:30 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:29 GMT

04/08/2017 14:26:29 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:28 GMT

04/08/2017 14:26:28 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:34 GMT

04/08/2017 14:26:34 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:33 GMT

04/08/2017 14:26:33 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:32 GMT

04/08/2017 14:26:32 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:32 GMT

04/08/2017 14:26:32 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:31 GMT

04/08/2017 14:26:31 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:31 GMT

04/08/2017 14:26:31 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:30 GMT

04/08/2017 14:26:30 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:30 GMT

04/08/2017 14:26:30 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:29 GMT

04/08/2017 14:26:29 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

04/08/2017 14:26:28 GMT

04/08/2017 14:26:28 GMT

Critical (3)

82000200

No Ranging Response received - T3 time-out

 

downstreamdownstreamupstreamupstream

0 Kudos
Reply
  • 16.13K
  • 1.34K
  • 3.27K
Superuser
Superuser
187 Views
Message 2 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping

Power levels and signal to noise ratio not the best, but shouldn't be having that amount of T3 issues, it would be around a week for the forum admin to reply, you could contact broadband support via 150 / 0345 454 1111
----------------------------------------------------------
If someone's helped you out say thanks by clicking on the thumbs up. If someone's solved your problem, why not mark their message as an Accepted Solution
0 Kudos
Reply
  • 6
  • 0
  • 0
junker404
Joining in
181 Views
Message 3 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping

thanks for the fast reply but I think I will wait to see if a forum support wizard picks this up, I did try the phone 150, but got tied up in a automated nightmare that checked the line said there was nothing wrong wait 10 mins then turn everything back on and then hung up on me
0 Kudos
Reply
  • 10.82K
  • 308
  • 631
Forum Team
Forum Team
158 Views
Message 4 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping

Afternoon junker404,

 

Thanks for posting and welcome to the community.

 

Sorry to read you are experiencing intermittent broadband connection.

 

Looking at your connection, the power levels are within range, there are no faults reported and the network segment is running stable, which is great. I was unable to find any issues that would cause these time-outs.

 

If you are still getting the same issue, can you re-post the network log for us to check over? Also it may be worth creating a Broadband Quality Monitor to check the performance of the connection. If you do set up the BQM make sure that you go into your router settings > Advanced Settings > Ping > and tick Respond to ICMP echo requests sent to WAN IP.

 

Speak to you soon

Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
  • 6
  • 0
  • 0
junker404
Joining in
143 Views
Message 5 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping




afternoon Sam
have been dropped a lot today
I have set up a BQM (although not sure what to do with yet)
and here are some logs from this morning


Network Log
First Time Last Time Priority Error Number Description
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:12:40 GMT 11/08/2017 11:12:40 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out

Network Log
First Time Last Time Priority Error Number Description
11/08/2017 11:28:56 GMT 11/08/2017 11:28:56 GMT Error (4) 68010302 DHCP WAN IP - 86.30.106.141
11/08/2017 11:27:57 GMT 11/08/2017 11:27:57 GMT Error (4) 68000407 TOD established
Time Not Established Time Not Established Critical (3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established Notice (6) 84000510 Downstream Locked Successfully
11/08/2017 11:17:42 GMT 11/08/2017 11:17:42 GMT Error (4) 68000407 TOD established
11/08/2017 11:17:33 GMT 11/08/2017 11:17:33 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:28 GMT 11/08/2017 11:17:28 GMT Notice (6) 84000510 Downstream Locked Successfully
11/08/2017 11:17:15 GMT 11/08/2017 11:17:15 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted
11/08/2017 11:17:15 GMT 11/08/2017 11:17:15 GMT Critical (3) 82000300 Ranging Request Retries exhausted
11/08/2017 11:17:13 GMT 11/08/2017 11:17:13 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:12 GMT 11/08/2017 11:17:12 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:11 GMT 11/08/2017 11:17:11 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:10 GMT 11/08/2017 11:17:10 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:09 GMT 11/08/2017 11:17:09 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:09 GMT 11/08/2017 11:17:09 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted
11/08/2017 11:17:09 GMT 11/08/2017 11:17:09 GMT Critical (3) 82000300 Ranging Request Retries exhausted
11/08/2017 11:17:07 GMT 11/08/2017 11:17:07 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:07 GMT 11/08/2017 11:17:07 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:06 GMT 11/08/2017 11:17:06 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:17:06 GMT 11/08/2017 11:17:06 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out

Network Log
First Time Last Time Priority Error Number Description
11/08/2017 11:41:53 GMT 11/08/2017 11:41:53 GMT Error (4) 68000407 TOD established
11/08/2017 11:41:46 GMT 11/08/2017 11:41:46 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:40 GMT 11/08/2017 11:41:40 GMT Notice (6) 84000510 Downstream Locked Successfully
11/08/2017 11:41:28 GMT 11/08/2017 11:41:28 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted
11/08/2017 11:41:28 GMT 11/08/2017 11:41:28 GMT Critical (3) 82000300 Ranging Request Retries exhausted
11/08/2017 11:41:27 GMT 11/08/2017 11:41:27 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:26 GMT 11/08/2017 11:41:26 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:25 GMT 11/08/2017 11:41:25 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:23 GMT 11/08/2017 11:41:23 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:23 GMT 11/08/2017 11:41:23 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted
11/08/2017 11:41:23 GMT 11/08/2017 11:41:23 GMT Critical (3) 82000300 Ranging Request Retries exhausted
11/08/2017 11:41:22 GMT 11/08/2017 11:41:22 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:21 GMT 11/08/2017 11:41:21 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:21 GMT 11/08/2017 11:41:21 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:20 GMT 11/08/2017 11:41:20 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:20 GMT 11/08/2017 11:41:20 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:19 GMT 11/08/2017 11:41:19 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:18 GMT 11/08/2017 11:41:18 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:18 GMT 11/08/2017 11:41:18 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 11:41:17 GMT 11/08/2017 11:41:17 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out

Network Log
First Time Last Time Priority Error Number Description
11/08/2017 12:22:11 GMT 11/08/2017 12:22:11 GMT Error (4) 68010302 DHCP WAN IP - removed 
11/08/2017 12:21:31 GMT 11/08/2017 12:21:31 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:21:30 GMT 11/08/2017 12:21:30 GMT Error (4) 68000407 TOD established
11/08/2017 12:21:20 GMT 11/08/2017 12:21:20 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:21:16 GMT 11/08/2017 12:21:16 GMT Notice (6) 84000510 Downstream Locked Successfully
11/08/2017 12:20:58 GMT 11/08/2017 12:20:58 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted
11/08/2017 12:20:58 GMT 11/08/2017 12:20:58 GMT Critical (3) 82000300 Ranging Request Retries exhausted
11/08/2017 12:20:57 GMT 11/08/2017 12:20:57 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:56 GMT 11/08/2017 12:20:56 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:55 GMT 11/08/2017 12:20:55 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:53 GMT 11/08/2017 12:20:53 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:52 GMT 11/08/2017 12:20:52 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:52 GMT 11/08/2017 12:20:52 GMT Critical (3) 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted
11/08/2017 12:20:52 GMT 11/08/2017 12:20:52 GMT Critical (3) 82000300 Ranging Request Retries exhausted
11/08/2017 12:20:51 GMT 11/08/2017 12:20:51 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:51 GMT 11/08/2017 12:20:51 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:50 GMT 11/08/2017 12:20:50 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:50 GMT 11/08/2017 12:20:50 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:48 GMT 11/08/2017 12:20:48 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
11/08/2017 12:20:48 GMT 11/08/2017 12:20:48 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out

[MOD EDIT: Personal and private information has been removed from this post. Please do not post personal or private information in your public posts. Please review the Forum Guidelines]

0 Kudos
Reply
  • 6
  • 0
  • 0
junker404
Joining in
142 Views
Message 6 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping

hope thats readable if not shout up and will screen grab instead of copy n paste
0 Kudos
Reply
  • 6
  • 0
  • 0
junker404
Joining in
111 Views
Message 7 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping

BQM result

 

My Broadband Ping - Graph 1
0 Kudos
Reply
  • 6
  • 0
  • 0
junker404
Joining in
99 Views
Message 8 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping

BQM

graph1.jpg

0 Kudos
Reply
  • 10.82K
  • 308
  • 631
Forum Team
Forum Team
55 Views
Message 9 of 9
Flag for a moderator

Re: vivid 200 super Hub 2 keeps dropping

Hiya junker404,

 

Thanks for getting back to me and for the additional information, I appreciate it.

 

As I am unable to find any issues on the line/network that would cause this, I think it's best if we arrange an engineer appointment to check this over. I've sent you a PM (purple envelope icon, right corner) with some details for you to confirm please.

 

In the meantime, with the network log you might see the time-outs showing the same date/time, if you can reset these it should show these correctly.

 

Speak to you soon

Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply