cancel
Showing results for 
Search instead for 
Did you mean: 

hub 3 randomly reboots itself

nvr
Joining in

My hub will randomly reboot itself, the connection drops, the green light appears, alongside the green broadband and green wifi flashing lights. After 5-10 minutes it reconnects.

I have manually rebooted, factory reset, and checked the interior cabling and all is good. I'd like to clarify that when it is connected, the internet connection is completely fine, speed is good, etc.

Lately, it seems to be getting more frequent, sometimes up to 5 times a day, and yet some days it will never reboot at all. I sometimes work from home and require it to be stable.

For further info, I found this thread which is an exact replica of my symptoms: https://community.virginmedia.com/t5/Networking-and-WiFi/Hub-3-0-random-rebooting-restarting-daily/m...

Going off of that linked thread it sounds like I need an engineer to check exterior cabling or cabinet.

Can someone from VM get this ball rolling without requiring me to sit on the phone 30mins+ please?

 

Your Hub 3.0 status
Wireless(On (2.4 and 5 GHz))
Internet(Partial Service (US only))

Downstream bonded channels

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

133075000013.340256 qam25
226675000012.538256 qam17
327475000012.840256 qam18
428275000012.538256 qam19
529075000012.540256 qam20
629875000013.138256 qam21
73067500001340256 qam22
831475000012.940256 qam23
932275000013.140256 qam24
103387500001340256 qam26
1134675000013.140256 qam27
1235475000013.540256 qam28
1336275000013.540256 qam29
143707500001340256 qam30
1537875000012.638256 qam31
1638675000011.938256 qam32
1739475000011.138256 qam33
1840275000010.838256 qam34
1941075000011.138256 qam35
2041875000011.540256 qam36
215227500001038256 qam37
225307500001038256 qam38
2353875000010.840256 qam39
2454675000010.838256 qam40



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.3577206
2Locked38.91060256
3Locked40.3901251
4Locked38.9826236
5Locked40.3794226
6Locked38.9688212
7Locked40.3632185
8Locked40.3641157
9Locked40.9531179
10Locked40.3442130
11Locked40.348291
12Locked40.341769
13Locked40.336791
14Locked40.336195
15Locked38.933270
16Locked38.934059
17Locked38.930377
18Locked38.928958
19Locked38.626051
20Locked40.325852
21Locked38.914351
22Locked38.915042
23Locked40.313644
24Locked38.915430

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13660000245.8512064 qam3
23009998847512064 qam4
34310000444.8512064 qam2
44959996944.3512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
2 REPLIES 2

nvr
Joining in

the network log looks like this:

Network Log

Time Priority Description

08/09/2023 17:09:0criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 17:07:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 17:07:25criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 17:06:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 17:06:58criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 17:06:30criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 17:05:35noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:56:30criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:54:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:54:0criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:50:11criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:49:25Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:48:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:45:11criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:43:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:43:27criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:43:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:43:7criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:42:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2023 16:42:47criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

and when it reboots I see things like this:

06/09/2023 16:15:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/09/2023 16:15:3criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/09/2023 16:15:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Hi nvr,

Thank you for reaching back out and for the above information, I was able to locate you on our system with the details we have for you and can see there is an issue in the area which is effecting multiple customers, there aren't currently any updates however this is being monitored.

How have things been since Friday?

Regards

Paul.