on 27-07-2021 15:25
https://www.thinkbroadband.com/broadband/monitoring/quality/share/06c030e1ed1492f564661c78163b2e7a7df18878-27-07-2021
on 27-07-2021 15:54
Doesn't look good. I suggest you connect to the hub by clicking on this link http://192.168.0.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log. You'll get an error message when you post the Network log, just click on "post" a second time.
Then we can check for any obvious problems with power, noise or error counts.
on 27-07-2021 17:25
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 3.7 | 38 | 256 qam | 25 |
2 | 203000000 | 4.6 | 38 | 256 qam | 9 |
3 | 211000000 | 4.5 | 38 | 256 qam | 10 |
4 | 219000000 | 4.6 | 38 | 256 qam | 11 |
5 | 227000000 | 4.5 | 38 | 256 qam | 12 |
6 | 235000000 | 4.5 | 38 | 256 qam | 13 |
7 | 243000000 | 4.3 | 38 | 256 qam | 14 |
8 | 251000000 | 4.3 | 38 | 256 qam | 15 |
9 | 259000000 | 4.1 | 38 | 256 qam | 16 |
10 | 267000000 | 4.1 | 38 | 256 qam | 17 |
11 | 275000000 | 3.9 | 38 | 256 qam | 18 |
12 | 283000000 | 3.9 | 38 | 256 qam | 19 |
13 | 291000000 | 3.7 | 38 | 256 qam | 20 |
14 | 299000000 | 4 | 38 | 256 qam | 21 |
15 | 307000000 | 3.9 | 38 | 256 qam | 22 |
16 | 315000000 | 3.7 | 38 | 256 qam | 23 |
17 | 323000000 | 3.7 | 38 | 256 qam | 24 |
18 | 339000000 | 3.7 | 38 | 256 qam | 26 |
19 | 347000000 | 3.5 | 38 | 256 qam | 27 |
20 | 355000000 | 3.7 | 38 | 256 qam | 28 |
21 | 363000000 | 3.7 | 38 | 256 qam | 29 |
22 | 371000000 | 3.7 | 38 | 256 qam | 30 |
23 | 379000000 | 3.7 | 38 | 256 qam | 31 |
24 | 387000000 | 3.7 | 38 | 256 qam | 32 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 30 | 0 |
2 | Locked | 38.6 | 31 | 0 |
3 | Locked | 38.6 | 23 | 0 |
4 | Locked | 38.9 | 25 | 0 |
5 | Locked | 38.6 | 36 | 0 |
6 | Locked | 38.6 | 21 | 0 |
7 | Locked | 38.9 | 23 | 0 |
8 | Locked | 38.9 | 22 | 0 |
9 | Locked | 38.9 | 19 | 0 |
10 | Locked | 38.6 | 26 | 0 |
11 | Locked | 38.9 | 28 | 0 |
12 | Locked | 38.6 | 26 | 0 |
13 | Locked | 38.6 | 25 | 0 |
14 | Locked | 38.9 | 29 | 0 |
15 | Locked | 38.6 | 20 | 0 |
16 | Locked | 38.6 | 22 | 0 |
17 | Locked | 38.9 | 27 | 0 |
18 | Locked | 38.6 | 17 | 0 |
19 | Locked | 38.6 | 23 | 0 |
20 | Locked | 38.9 | 17 | 0 |
21 | Locked | 38.6 | 22 | 0 |
22 | Locked | 38.9 | 17 | 0 |
23 | Locked | 38.9 | 24 | 0 |
24 | Locked | 38.9 | 17 | 0 |
on 27-07-2021 18:42
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 36.5 | 5120 | 64 qam | 10 |
2 | 39400000 | 35 | 5120 | 64 qam | 12 |
3 | 46200000 | 35 | 5120 | 64 qam | 11 |
4 | 60300000 | 36.5 | 5120 | 64 qam | 9 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 27-07-2021 18:43
General Configuration
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | kfoA,.iyewrkldJKDHSUBsgvc |
Primary Downstream Service Flow
SFID | 15392 |
Max Traffic Rate | 575000000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 15391 |
Max Traffic Rate | 38520000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
on 27-07-2021 18:44
TimePriorityDescription27/07/2021 16:22:1noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/07/2021 16:20:58Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/07/2021 03:25:24noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/07/2021 03:25:24ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;23/07/2021 13:09:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;23/07/2021 10:24:15noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;23/07/2021 10:24:15ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;21/07/2021 04:59:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;20/07/2021 15:07:0noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;20/07/2021 15:07:0ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;16/07/2021 00:58:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;15/07/2021 16:41:34noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;15/07/2021 16:41:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;12/07/2021 08:33:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;12/07/2021 04:41:35noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;12/07/2021 04:41:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;10/07/2021 04:34:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;08/07/2021 16:41:36noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;08/07/2021 16:41:36ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;06/07/2021 00:41:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
on 28-07-2021 01:00
https://www.thinkbroadband.com/broadband/monitoring/quality/share/4be84993a42db8ea66c54bac4dd5c2f6bbf13538
Live link
on 28-07-2021 05:04
Nothing obviously wrong with the hub stats, although the upstream power is bouncing along at the very lower end of the accepted range, and I suspect is the probable cause. I'll mark for the forum staff to advise.
They may be able to see something not visible in the snapshot of hub stats you and I can see. If you get a "looks good from our side" response you may need to be persistent - the BQM shows there is a problem.
on 28-07-2021 08:48
Good morning @halifax1983
Welcome back to the forums and thank you for taking the time to post.
I have taken a look over your services from our end and can see the we will need to get an engineer out to come and look at your power levels.
I will pop you over a PM so that I can get some account information.
Kind regards,
Zak_M
on 29-07-2021 13:52
Good afternoon @halifax1983
Thank you for providing me with that information via PM.
I have booked the engineer for you, for the time, date & to make any amendments, you can visit your My virgin media account.
Kind regards,
Zak_M