on 10-09-2023 15:23
I’ve been having intermittent connection problems with my Hub5 for the last week. Internet would just drop out completely when trying to do any upload (even backing up my WhatsApp would cause it to crash. The router would flash red then reboot itself. I’ve done a pinhole reset and regularly rebooted but it’s been disconnecting a lot. I ran the network diagnostic test via the MyVirginMedia app and it said there is a fault. I booked a technician to come out on Friday and he said it looked okay but seemed to be some interference from an Ethernet source. He told me to unplug all the Ethernet cables and to monitor for a couple of days. I’ve ran another test today on the connection and it’s saying to book another technician as there still appears to be an issue with the connection?? When I log into the router and look into the advanced settings network diagnostics log there’s lots of errors but I don’t understand them can anyone help at all?.
on 11-09-2023 15:21
Can you do this..
_______________
Post up your Hub/network connection details and someone will check to see if there is a problem there. In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return. No need to log in - just click on the “Router Status” icon/text at bottom-middle (Hub3/4/5) or top/right (SH’s) - of the Login page.
Then… Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts
Also,
If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then, click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK
https://www.thinkbroadband.com/broadband/monitoring/quality
on 11-09-2023 21:44
Downstream bonded channels
1 | 147000000 | 6.9 | 41 | QAM 256 | 2 |
2 | 139000000 | 6.8 | 41 | QAM 256 | 1 |
3 | 155000000 | 6.8 | 41 | QAM 256 | 3 |
4 | 163000000 | 6.7 | 41 | QAM 256 | 4 |
5 | 171000000 | 6.4 | 41 | QAM 256 | 5 |
6 | 179000000 | 6.5 | 41 | QAM 256 | 6 |
7 | 187000000 | 6.4 | 41 | QAM 256 | 7 |
8 | 195000000 | 6.6 | 41 | QAM 256 | 8 |
9 | 203000000 | 6.3 | 41 | QAM 256 | 9 |
10 | 211000000 | 6.5 | 41 | QAM 256 | 10 |
11 | 219000000 | 6.3 | 41 | QAM 256 | 11 |
12 | 227000000 | 6.2 | 40 | QAM 256 | 12 |
13 | 235000000 | 6.1 | 41 | QAM 256 | 13 |
14 | 243000000 | 6 | 40 | QAM 256 | 14 |
15 | 251000000 | 5.8 | 40 | QAM 256 | 15 |
16 | 259000000 | 5.7 | 41 | QAM 256 | 16 |
17 | 267000000 | 5.8 | 41 | QAM 256 | 17 |
18 | 275000000 | 5.6 | 40 | QAM 256 | 18 |
19 | 283000000 | 5.8 | 41 | QAM 256 | 19 |
20 | 291000000 | 5.8 | 41 | QAM 256 | 20 |
21 | 299000000 | 6.8 | 41 | QAM 256 | 21 |
22 | 307000000 | 6.9 | 41 | QAM 256 | 22 |
23 | 315000000 | 7.1 | 41 | QAM 256 | 23 |
24 | 323000000 | 6.6 | 41 | QAM 256 | 24 |
25 | 363000000 | 5.9 | 41 | QAM 256 | 25 |
26 | 371000000 | 5.8 | 41 | QAM 256 | 26 |
27 | 379000000 | 5.6 | 41 | QAM 256 | 27 |
28 | 387000000 | 5.7 | 41 | QAM 256 | 28 |
29 | 395000000 | 5.6 | 41 | QAM 256 | 29 |
30 | 403000000 | 5.5 | 41 | QAM 256 | 30 |
31 | 411000000 | 4.9 | 41 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 41 | 47454 | 6501 |
2 | Locked | 41 | 8417 | 987 |
3 | Locked | 41 | 25711 | 4078 |
4 | Locked | 41 | 14785 | 2229 |
5 | Locked | 41 | 844 | 93 |
6 | Locked | 41 | 33310 | 5417 |
7 | Locked | 41 | 36840 | 6125 |
8 | Locked | 41 | 35309 | 5974 |
9 | Locked | 41 | 26818 | 4362 |
10 | Locked | 41 | 24641 | 4371 |
11 | Locked | 41 | 5549 | 792 |
12 | Locked | 40 | 13991 | 2986 |
13 | Locked | 41 | 280 | 24 |
14 | Locked | 40 | 19453 | 4024 |
15 | Locked | 40 | 22997 | 4346 |
16 | Locked | 41 | 4628 | 807 |
17 | Locked | 41 | 24226 | 5229 |
18 | Locked | 40 | 13154 | 5598 |
19 | Locked | 41 | 14324 | 3608 |
20 | Locked | 41 | 3574 | 2078 |
21 | Locked | 41 | 2986 | 756 |
22 | Locked | 41 | 2775 | 855 |
23 | Locked | 41 | 2815 | 775 |
24 | Locked | 41 | 110 | 0 |
25 | Locked | 41 | 5246 | 1861 |
26 | Locked | 41 | 94 | 0 |
27 | Locked | 41 | 8509 | 3366 |
28 | Locked | 41 | 2386 | 878 |
29 | Locked | 41 | 2336 | 1050 |
30 | Locked | 41 | 8151 | 2831 |
31 | Locked | 41 | 9271 | 3274 |
Upstream bonded channels
0 | 49600000 | 47.3 | 5120 | QAM 64 | 1 |
1 | 43100000 | 47 | 5120 | QAM 64 | 2 |
2 | 36600000 | 47.5 | 5120 | QAM 64 | 3 |
3 | 30100000 | 47.5 | 5120 | QAM 64 | 4 |
4 | 23600000 | 47 | 5120 | QAM 64 | 5 |
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 | 0 | 0 |
Network Log
10-09-2023 23:39:44 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-09-2023 23:39:44 | 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; |
10-09-2023 22:37:58 | 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; |
10-09-2023 22:37:58 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
10-09-2023 14:47:53 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:52:20 | warning | Dynamic Range Window violation |
09-09-2023 17:52:20 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:34:36 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:34:36 | 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; |
09-09-2023 17:09:11 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:07:44 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:07:02 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 18 20; 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; |
09-09-2023 17:06:38 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 20; 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; |
09-09-2023 17:06:33 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:06:17 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 20; 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; |
09-09-2023 17:04:23 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:04:12 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 18; 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; |
09-09-2023 17:04:09 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:04:09 | 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; |
09-09-2023 17:03:56 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 20; 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; |
09-09-2023 17:03:43 | 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; |
09-09-2023 17:03:41 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 18; 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; |
09-09-2023 17:03:25 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 20; 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; |
09-09-2023 17:03:11 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 18; 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; |
09-09-2023 17:02:56 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 20; 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; |
09-09-2023 17:02:52 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:02:43 | error | DBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:02:40 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 17:02:40 | 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; |
09-09-2023 17:02:39 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 18 20; 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; |
09-09-2023 17:02:28 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-09-2023 06:14:54 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 11-09-2023 22:35
Too many errors, but the figures are accumulative since the hub was last power cycled. So please turn off your hub for a short period, this will reset the counters, then post a new full set of stats after about two hours. This will indicate the current line status.
on 14-09-2023 11:24
Hi there mattymatt1980,
Thanks for your post and welcome back to the community.
Many apologies for the problems faced with your service, just from checking our system however I can't seem to find any readings that would attribute to the issue you're having.
Are you able to post another set of stats as advised after the reboot?
Let us know,
on 16-09-2023 09:44
Here are the latest set. I rebooted last night.
Downstream bonded channels
1 | 147000000 | 7.3 | 41 | QAM 256 | 2 |
2 | 139000000 | 7.2 | 41 | QAM 256 | 1 |
3 | 155000000 | 7.2 | 41 | QAM 256 | 3 |
4 | 163000000 | 7.1 | 40 | QAM 256 | 4 |
5 | 171000000 | 6.7 | 41 | QAM 256 | 5 |
6 | 179000000 | 6.9 | 41 | QAM 256 | 6 |
7 | 187000000 | 6.8 | 41 | QAM 256 | 7 |
8 | 195000000 | 7.1 | 41 | QAM 256 | 8 |
9 | 203000000 | 6.7 | 41 | QAM 256 | 9 |
10 | 211000000 | 6.9 | 40 | QAM 256 | 10 |
11 | 219000000 | 6.7 | 40 | QAM 256 | 11 |
12 | 227000000 | 6.6 | 40 | QAM 256 | 12 |
13 | 235000000 | 6.5 | 40 | QAM 256 | 13 |
14 | 243000000 | 6.4 | 40 | QAM 256 | 14 |
15 | 251000000 | 6.3 | 40 | QAM 256 | 15 |
16 | 259000000 | 6.2 | 40 | QAM 256 | 16 |
17 | 267000000 | 6.4 | 40 | QAM 256 | 17 |
18 | 275000000 | 6.2 | 40 | QAM 256 | 18 |
19 | 283000000 | 6.4 | 40 | QAM 256 | 19 |
20 | 291000000 | 6.3 | 40 | QAM 256 | 20 |
21 | 299000000 | 7.2 | 40 | QAM 256 | 21 |
22 | 307000000 | 7.4 | 41 | QAM 256 | 22 |
23 | 315000000 | 7.6 | 41 | QAM 256 | 23 |
24 | 323000000 | 7.1 | 41 | QAM 256 | 24 |
25 | 363000000 | 6.5 | 41 | QAM 256 | 25 |
26 | 371000000 | 6.4 | 41 | QAM 256 | 26 |
27 | 379000000 | 6.3 | 41 | QAM 256 | 27 |
28 | 387000000 | 6.5 | 41 | QAM 256 | 28 |
29 | 395000000 | 6.4 | 41 | QAM 256 | 29 |
30 | 403000000 | 6.4 | 41 | QAM 256 | 30 |
31 | 411000000 | 5.7 | 41 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 41 | 13089 | 2501 |
2 | Locked | 41 | 30469 | 3198 |
3 | Locked | 41 | 70959 | 8519 |
4 | Locked | 40 | 13236 | 1764 |
5 | Locked | 41 | 11465 | 2103 |
6 | Locked | 41 | 28313 | 3794 |
7 | Locked | 41 | 11858 | 1452 |
8 | Locked | 41 | 25012 | 4138 |
9 | Locked | 41 | 3481 | 526 |
10 | Locked | 40 | 3156 | 530 |
11 | Locked | 40 | 3045 | 533 |
12 | Locked | 40 | 4847 | 1212 |
13 | Locked | 40 | 4450 | 1331 |
14 | Locked | 40 | 2452 | 548 |
15 | Locked | 40 | 4084 | 1393 |
16 | Locked | 40 | 6069 | 1518 |
17 | Locked | 40 | 3539 | 1206 |
18 | Locked | 40 | 3344 | 1200 |
19 | Locked | 40 | 1727 | 572 |
20 | Locked | 40 | 1598 | 517 |
21 | Locked | 40 | 3685 | 1745 |
22 | Locked | 41 | 1295 | 561 |
23 | Locked | 41 | 1307 | 530 |
24 | Locked | 41 | 2313 | 1089 |
25 | Locked | 41 | 1169 | 428 |
26 | Locked | 41 | 5773 | 2805 |
27 | Locked | 41 | 2727 | 1627 |
28 | Locked | 41 | 2166 | 1028 |
29 | Locked | 41 | 1079 | 501 |
30 | Locked | 41 | 5269 | 2889 |
31 | Locked | 41 | 2604 | 1651 |
Upstream bonded channels
0 | 49600000 | 47.3 | 5120 | QAM 64 | 1 |
1 | 43100000 | 47.3 | 5120 | QAM 64 | 2 |
2 | 36600000 | 47.8 | 5120 | QAM 64 | 3 |
3 | 30100000 | 47.5 | 5120 | QAM 64 | 4 |
4 | 23600000 | 46.8 | 5120 | QAM 64 | 5 |
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 | 0 | 0 |
Network Log
16-09-2023 09:50:05 | 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; |
16-09-2023 09:41:22 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 09:37:05 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 09:32:19 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 09:29:44 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 06:37:39 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 06:37:39 | warning | Dynamic Range Window violation |
16-09-2023 02:17:04 | warning | Dynamic Range Window violation |
16-09-2023 02:17:04 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:06:02 | 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; |
16-09-2023 01:06:02 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:58 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
16-09-2023 01:05:51 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:51 | warning | Dynamic Range Window violation |
16-09-2023 01:05:51 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:51 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:51 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:51 | warning | Dynamic Range Window violation |
16-09-2023 01:05:51 | warning | Dynamic Range Window violation |
16-09-2023 01:05:51 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:51 | warning | Dynamic Range Window violation |
16-09-2023 01:05:51 | warning | Dynamic Range Window violation |
16-09-2023 01:05:51 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:51 | warning | Dynamic Range Window violation |
16-09-2023 01:05:51 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:46 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:34 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:31 | notice | Honoring MDD; IP provisioning mode = IPv4 |
16-09-2023 01:05:22 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
16-09-2023 01:05:09 | critical | Cable Modem reboot from UI |
13-09-2023 19:58:12 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
13-09-2023 19:58:12 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 16-09-2023 09:45
Network diagnostics in the hub settings itself says this.
on 18-09-2023 11:32
Hi @mattymatt1980 thanks for your reply.
It does seem that after running checks, all the levels to your Hub are within the specifications so there's no cause for concern here.
We'd advise please continuing to monitor the connection but if everything does seem fine in terms of the connection, we would advise bypassing the error logs you see.
If things deteriorate please don't hesitate to let us know.
Many thanks