Menu
Reply
Hayley_S
  • 3.9K
  • 129
  • 255
Forum Team (Retired)
Forum Team (Retired)
465 Views
Message 21 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Hello @shak2,

Welcome back, thanks for posting.

I am sorry for any issues with your Hub-4.

I located your account using your forums details, I am unable to see any issues with your Wi-Fi connection. Also your equipment is not showing any known errors on there. Please can you try doing a pinhole reset? Let me know how it goes.

Many thanks,

Hayley
Forum Team



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


0 Kudos
Reply
shak2
  • 18
  • 0
  • 1
Tuning in
452 Views
Message 22 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Dear Hayley

Please see my last post  as this issue is now fixed.

Kath_F
  • 34.21K
  • 1.31K
  • 2.77K
Forum Team
Forum Team
439 Views
Message 23 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Hi Shak2, 

Thanks for coming back to us and updating the thread to let us know things are sorted for you now. 

If you have any further issues, you know where we are. 

Take care and enjoy your weekend. 

Thanks, 

Kath_F
Forum Team


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


shak2
  • 18
  • 0
  • 1
Tuning in
430 Views
Message 24 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Thanks

 I am hoping others havig similar issues catch on to this and I sincerely hope its sorted for them too as I understand how it can really discourage someone especially when Virgin Media Is the BEST for Broadband .

0 Kudos
Reply
Kath_F
  • 34.21K
  • 1.31K
  • 2.77K
Forum Team
Forum Team
417 Views
Message 25 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Hi shak2, 

Of course. We do always work hard to get any issues that customer's are experiencing put right and sometimes it may take us longer than we'd like but we don't give up. 

For now, enjoy the connection as it's working as it should be 🙂

Take care,

Kath_F
Forum Team


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


0 Kudos
Reply
TooManyShoes
  • 16
  • 0
  • 0
Joining in
192 Views
Message 26 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Hi,

I am having a very similar issue here. Had VM here for 3 and a half years and been excellent speed and stability. Upgraded to 1gb broadband end of August and VM replaced our hub 3 with a hub 4. Since then hub auto reboots minimum once a day but often more. I also work from home so this is a real issue. Have had an engineer out who said he "boosted" the signal but the problem remains. Before you ask have tried resetting hub, have got new wifi pods, have checked all cable connections. The only ethernet connection I have is the Tivo box, everything else is wifi. Have just set up a BQM now and link is here:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/76952ee97d53c7e5f7f01d3ae71e3136ab... 

Thanks 

0 Kudos
Reply
TooManyShoes
  • 16
  • 0
  • 0
Joining in
191 Views
Message 27 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

3.0 Downstream channels

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

25330750000-4.138.6QAM25625
1138750000-3.138.6QAM2561
2146750000-3.438.6QAM2562
3154750000-3.838.6QAM2563
4162750000-3.738.6QAM2564
5170750000-3.838.6QAM2565
6178750000-438.6QAM2566
7186750000-3.838.6QAM2567
8194750000-3.938.6QAM2568
9202750000-4.138.6QAM2569
10210750000-4.138.6QAM25610
11218750000-4.238.6QAM25611
12226750000-4.138.6QAM25612
13234750000-4.538.6QAM25613
14242750000-4.738.6QAM25614
15250750000-5.237.6QAM25615
16258750000-5.437.6QAM25616
17266750000-5.537.6QAM25617
18274750000-5.537.6QAM25618
19282750000-5.237.6QAM25619
20290750000-4.737.6QAM25620
21298750000-4.238.6QAM25621
22306750000-4.238.6QAM25622
23314750000-4.338.6QAM25623
24322750000-4.138.6QAM25624
26338750000-3.739QAM25626
27346750000-3.839QAM25627
28354750000-438.6QAM25628
29362750000-4.139QAM25629
30370750000-4.138.6QAM25630
31378750000-3.939QAM25631



3.0 Downstream channels

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

25Locked38.60537700
1Locked38.60537700
2Locked38.60537700
3Locked38.60537700
4Locked38.60537700
5Locked38.60537700
6Locked38.60537700
7Locked38.60537700
8Locked38.60537700
9Locked38.60537700
10Locked38.60537700
11Locked38.60537700
12Locked38.60537700
13Locked38.60537700
14Locked38.60537700
15Locked37.63627600
16Locked37.63627600
17Locked37.63627600
18Locked37.63627600
19Locked37.63627600
20Locked37.63627600
21Locked38.60537700
22Locked38.60537700
23Locked38.60537700
24Locked38.60537700
26Locked38.98326100
27Locked38.98326100
28Locked38.60537700
29Locked38.98326100
30Locked38.60537700
31Locked38.98326100



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
37944K1840QAM4096424


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
37Locked40-5.37944489624
0 Kudos
Reply
TooManyShoes
  • 16
  • 0
  • 0
Joining in
190 Views
Message 28 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

3.0 Upstream channels

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

146200000415120 KSym/sec64QAM6
25370000042.35120 KSym/sec64QAM5
33940000040.55120 KSym/sec64QAM7
43260000040.35120 KSym/sec64QAM8



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

 

0 Kudos
Reply
TooManyShoes
  • 16
  • 0
  • 0
Joining in
189 Views
Message 29 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Network Log

Time Priority Description

Wed 12/10/2022 14:12:475MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 12/10/2022 14:34:246CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 12/10/2022 22:56:543No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/10/2022 14:34:336CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 14/10/2022 05:43:243No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 14/10/2022 08:46:374DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 14/10/2022 14:34:246CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/10/2022 14:32:395MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/10/2022 21:00:236CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/10/2022 12:47:575MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 17/10/2022 14:34:196CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 18/10/2022 04:07:555MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 18/10/2022 05:38:503No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 18/10/2022 12:39:096CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 19/10/2022 17:41:215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 19/10/2022 21:35:205MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 20/10/2022 00:09:426CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 20/10/2022 22:47:475MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 20/10/2022 23:15:146CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 21/10/2022 14:02:335MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 21/10/2022 14:02:445RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 21/10/2022 14:02:536CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 21/10/2022 23:28:265MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 21/10/2022 23:28:365RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 21/10/2022 23:29:036CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 22/10/2022 04:56:435MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 22/10/2022 08:19:065MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:193No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 22/10/2022 13:15:155MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 22/10/2022 16:14:186CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:183No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 22/10/2022 18:58:195MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 22/10/2022 19:24:576CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:183No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 23/10/2022 01:33:145MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Natalie_L
  • 6.33K
  • 232
  • 490
Forum Team
Forum Team
168 Views
Message 30 of 43
Flag for a moderator

Re: Hub 4 reboots Every night

Hi TooManyShoes, 

Thank you for your post to us here on the Community. 

I am sorry to hear you are experiencing issues with your broadband service. 

I have taken a look from our side and cannot see any issue in your area and your Hub appears to be running within specification. 

To confirm, is your Hub dropping at certain times like the issue stated in the original post? 

Thanks, 

 

Nat
0 Kudos
Reply