on 10-05-2019 00:16
I am having nonstop issues with the Super hub 3 router that keeps resetting rebooting itself since the past few weeks. All wired and wifi connections drop until the reboot is complete and then everything starts working again. This happens at least 7-8 times a day sometimes more. Various complaints made via telephone to Virgin Media who don't appear to care. All phones for technical faults are handled by call takers in India who read from a script and it appears that they don't have a clue about the issues. I have resorted to taking the matter through ADR scheme through the regulators to seek Virgin media bosses attention on this issue as they appear to not really be bothered. Virgin Media will not send a tech out or replace the router and frankly are an appalling company to deal with. Any one have a fix for this?
Answered! Go to Answer
on 10-05-2019 14:41
Or the easier way.
Navigate to http://192.168.0.1 and click Check router status bottom centre of the screen, without logging in.
on 10-05-2019 18:30
Yep, spot on.
The logs are showing the local circuit dropping, so VM need to take a closer look.
on 10-05-2019 13:54
Hi badger999, welcome to our community forums.
Are you able to provide the times that you've been experiencing these drop outs?
Would you also be able to log into your hub settings to post the Network Status results including the Network Log as this will show any errors or stats from your connection that would indicate any concerns on the connection.
Thanks,
Tom_S
on 10-05-2019 14:17
How do I find the network log? There are no set times and the hub just reboots itself every few hours. I am so fed up with Virgin customer service.
on 10-05-2019 14:22
Apologies, you can access the Network Status by following the instructions provided in the link provided in the previous post to log into the hub settings, then go to Advanced Settings, then Tools and then Network Status.
At that point you should be able to just highlight, copy & paste, or take screenshots.
When posting the results here please make sure to obscure any personal details such as the MAC address as if those details are visible the mods will potentially remove any pictures or edit any posts with those details.
Thanks,
Tom_S
on 10-05-2019 14:41
Or the easier way.
Navigate to http://192.168.0.1 and click Check router status bottom centre of the screen, without logging in.
on 10-05-2019 18:13
on 10-05-2019 18:25
Network Log
Time Priority Description
10/05/2019 16:13:10 | critical | No Ranging Response received - T3 time-out;CM-MAC=XXXXXXXXX:7b;CMTS-MAC=XXXXXXX;CM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:13:15 | Warning! | RCS Partial Service;CM-MAC=XXCMTS-MAC=XX-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:13:15 | critical | No Ranging Response received - T3 time-out;CM-MAC=xb;CMTS-MAC=xM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:13:25 | Warning! | RCS Partial Service;CM-MAC=xCMTS-MAC=fx1.1;CM-VER=3.0; |
10/05/2019 16:13:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:13:34 | Warning! | RCS Partial Service;CM-MAC=4xMTS-MAC=xCM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:14:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=xCMTS-MACx CM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:14:28 | Warning! | RCS Partial Service;CM-MAC=x;CMTS-MAC=xCM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:14:47 | critical | No Ranging Response received - T3 time-out;CM-MAC=x7b;CMTS-MAC=fxCM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:16:24 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=x:7b;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:16:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=x7b;CMTS-MAC=xCM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:17:42 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=x7b;CMTS-MACx-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:17:43 | critical | No Ranging Response received - T3 time-out;CM-MACx:7b;CMTS-MAC=x-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:18:6 | Warning! | RCS Partial Service;CM-MAC=x:7b;CMTS-MAC=xCM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:18:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=xCMTS-MAC=xaf;CM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:19:22 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=x7b;CMTS-MAC=xQOS=1.1;CM-VER=3.0; |
10/05/2019 16:19:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=x7b;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:20:2 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=x;CMTS-MAC=xCM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:20:2 | critical | No Ranging Response received - T3 time-out;CM-MACx;CMTS-MAC=xCM-QOS=1.1;CM-VER=3.0; |
10/05/2019 16:28:22 | Warning! | RCS Partial Service;CM-MAC=xb;CMTS-MAC=xCM-QOS=1.1;CM-VER=3.0; |
on 10-05-2019 18:25
on 10-05-2019 18:30
Yep, spot on.
The logs are showing the local circuit dropping, so VM need to take a closer look.
on 10-05-2019 18:56