on 16-04-2023 19:19
Hi all, I recently changed my virgin package and I was provided with a new Hub 5 router. I have 3 wifi pods also connected. I keep getting WIFI drop outs from the internet roughly every 2 hours. Mainly noticing this on my tv which is connected by Ethernet to the router when I’m watching something like Disney+ or Amazon Prime etc. It also states on the app that there has been an internet connection issue. Anyone else been having issues with their hub 5
Thanks
on 16-04-2023 19:47
on 19-04-2023 08:04
Hi Iotharmat, sorry for the delayed reply. Let me upload the files as requested.
Status
Acquired Downstream Channel(Hz) | 331000000 | Locked |
Ranged Upstream Channel(Hz) | 49600000 | Ranged |
Provisioning State | Online | Operational |
on 19-04-2023 08:05
Downstream
Downstream bonded channels
1 | 331000000 | 0.4 | 41 | QAM 256 | 25 |
2 | 139000000 | 0.1 | 40 | QAM 256 | 1 |
3 | 147000000 | 0 | 40 | QAM 256 | 2 |
4 | 155000000 | 0.1 | 40 | QAM 256 | 3 |
5 | 163000000 | 0.3 | 40 | QAM 256 | 4 |
6 | 171000000 | 0.4 | 40 | QAM 256 | 5 |
7 | 179000000 | 0.4 | 41 | QAM 256 | 6 |
8 | 187000000 | 0.5 | 41 | QAM 256 | 7 |
9 | 195000000 | 0.4 | 41 | QAM 256 | 8 |
10 | 203000000 | 0.5 | 41 | QAM 256 | 9 |
11 | 211000000 | 0.4 | 41 | QAM 256 | 10 |
12 | 219000000 | 0.5 | 41 | QAM 256 | 11 |
13 | 227000000 | 0.7 | 41 | QAM 256 | 12 |
14 | 235000000 | 0.9 | 41 | QAM 256 | 13 |
15 | 243000000 | -1 | 41 | QAM 256 | 14 |
16 | 251000000 | -1.1 | 41 | QAM 256 | 15 |
17 | 259000000 | 0.3 | 41 | QAM 256 | 16 |
18 | 267000000 | 0 | 41 | QAM 256 | 17 |
19 | 275000000 | 0.2 | 41 | QAM 256 | 18 |
20 | 283000000 | 0.2 | 41 | QAM 256 | 19 |
21 | 291000000 | 0.3 | 41 | QAM 256 | 20 |
22 | 299000000 | 0.3 | 41 | QAM 256 | 21 |
23 | 307000000 | 0.3 | 41 | QAM 256 | 22 |
24 | 315000000 | 0 | 41 | QAM 256 | 23 |
25 | 323000000 | 0.1 | 41 | QAM 256 | 24 |
26 | 339000000 | 0.4 | 40 | QAM 256 | 26 |
27 | 347000000 | 0.2 | 41 | QAM 256 | 27 |
28 | 355000000 | 0.4 | 41 | QAM 256 | 28 |
29 | 363000000 | 0.5 | 41 | QAM 256 | 29 |
30 | 371000000 | 0.6 | 41 | QAM 256 | 30 |
31 | 379000000 | 0.7 | 41 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 41 | 126 | 45 |
2 | Locked | 40 | 110 | 0 |
3 | Locked | 40 | 517 | 28 |
4 | Locked | 40 | 1614 | 181 |
5 | Locked | 40 | 1080 | 213 |
6 | Locked | 40 | 814 | 156 |
7 | Locked | 41 | 1202 | 199 |
8 | Locked | 41 | 143 | 161 |
9 | Locked | 41 | 62 | 43 |
10 | Locked | 41 | 231 | 156 |
11 | Locked | 41 | 335 | 179 |
12 | Locked | 41 | 192 | 189 |
13 | Locked | 41 | 127 | 156 |
14 | Locked | 41 | 218 | 151 |
15 | Locked | 41 | 644 | 100 |
16 | Locked | 41 | 1137 | 98 |
17 | Locked | 41 | 756 | 73 |
18 | Locked | 41 | 220 | 82 |
19 | Locked | 41 | 111 | 77 |
20 | Locked | 41 | 111 | 77 |
21 | Locked | 41 | 110 | 61 |
22 | Locked | 41 | 172 | 60 |
23 | Locked | 41 | 130 | 56 |
24 | Locked | 41 | 128 | 44 |
25 | Locked | 41 | 127 | 52 |
26 | Locked | 40 | 174 | 30 |
27 | Locked | 41 | 149 | 42 |
28 | Locked | 41 | 1279 | 54 |
29 | Locked | 41 | 203 | 49 |
30 | Locked | 41 | 131 | 34 |
31 | Locked | 41 | 134 | 35 |
on 19-04-2023 08:07
Upstream
Upstream bonded channels
0 | 49600000 | 52.8 | 5120 | QAM 64 | 9 |
1 | 43100000 | 52.3 | 5120 | QAM 64 | 10 |
2 | 36600000 | 51.8 | 5120 | QAM 64 | 11 |
3 | 30100000 | 51.8 | 5120 | QAM 64 | 12 |
4 | 23600000 | 51.5 | 5120 | QAM 64 | 13 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 4 | 0 |
on 19-04-2023 08:08
Configuration
General Configuration
Allowed |
3 |
Enabled |
3.1 |
ewrkldJKDHSUBsgvca69834ncxv98 |
Primary Downstream Service Flow
6022 |
690000278 bps |
42600bytes |
0 bps |
7004 |
128000 bps |
4000bytes |
0 bps |
Primary Upstream Service Flow
2218 |
44000278 bps |
42600bytes |
0 bps |
42600bytes |
Best Effort |
6641 |
128000 bps |
4000bytes |
0 bps |
1522bytes |
Best Effort |
on 19-04-2023 08:09
Network Log
Network Log
19-04-2023 07:06:25 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-04-2023 07:05:25 | error | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-04-2023 07:05:22 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-04-2023 07:05:22 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 23:54:28 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 23:53:12 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 23:53:00 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 21:21:34 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 21:20:18 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 21:20:00 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 21:09:38 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 21:08:07 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 21:07:52 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 17:59:39 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 17:58:15 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 17:58:06 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 17:29:40 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 17:28:13 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 17:28:01 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 15:20:58 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 13:37:16 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 13:35:57 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 13:35:47 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 10:32:10 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 10:30:52 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 10:30:51 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 08:22:00 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 08:20:53 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 08:20:25 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 02:14:21 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 02:13:09 | notice | CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-04-2023 02:12:51 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 19-04-2023 08:11
Hi Iotharmat,
Thanks for your help with this. Hope the above is what you were looking for.
PS noticing a few people with the same issues and a few people are saying the issue has been fixed with getting their hub 5 swapped out for a hub 4.....
on 19-04-2023 08:18
The 3.0 Downstream channels are recording Post RS ( uncorrected ) errors. Observe to see if the figures are stable or rising.
The 3.0 Upstream Power levels are all high, 35 - 49 dBmV is the preferred range & we see 51.5 to 52.3 dBmV on this connection meaning the Hub is transmitting very strongly to the street cabinet.
on 19-04-2023 08:34
Hi Client62. Thanks for getting back to me with the above information.
I have phoned VM and they have said they will send an engineer out this Friday (21st). Hopefully they will be able to fix the issue but going by other similar posts it seems the VM engineers don't tend to be able to fix these issues on 1 visit. Time will tell I guess.