on 05-12-2023 15:32
Hi can my parents connection get fixed please its been months now. Engineer reported that networks confirmed bad snr for south bristol yet no ticket or fault number was created. I don't know what constitutes a bad connection in 2023 but I think this counts? 1000s of post rs errors bqm terrible error log shows this also power to high on 3.1. They were put on the hub 5 to try ro hide this yet there package is only m125 so hub 5 not needed?. This network is not coping in South bristol we all have problems but that's a different story. Specs below thanks.
1 | Locked | 41 | 135 | 54 |
2 | Locked | 39 | 429 | 985 |
3 | Locked | 40 | 649 | 796 |
4 | Locked | 40 | 665 | 386 |
5 | Locked | 40 | 978 | 663 |
6 | Locked | 40 | 672 | 340 |
7 | Locked | 40 | 999 | 385 |
8 | Locked | 40 | 1189 | 511 |
9 | Locked | 40 | 1218 | 413 |
10 | Locked | 41 | 8 | 0 |
11 | Locked | 41 | 6 | 0 |
12 | Locked | 41 | 147 | 830 |
13 | Locked | 41 | 813 | 500 |
14 | Locked | 41 | 354 | 301 |
15 | Locked | 41 | 63 | 39 |
16 | Locked | 41 | 24 | 32 |
17 | Locked | 41 | 117 | 232 |
18 | Locked | 41 | 109 | 249 |
19 | Locked | 41 | 107 | 216 |
20 | Locked | 41 | 97 | 204 |
21 | Locked | 41 | 116 | 157 |
22 | Locked | 41 | 151 | 106 |
23 | Locked | 41 | 133 | 79 |
24 | Locked | 41 | 78 | 52 |
25 | Locked | 41 | 121 | 57 |
26 | Locked | 41 | 148 | 29 |
27 | Locked | 41 | 105 | 32 |
28 | Locked | 41 | 81 | 31 |
29 | Locked | 41 | 122 | 48 |
30 | Locked | 41 | 116 | 50 |
31 | Locked | 41 | 115 | 43 |
3.1 Downstream channels
33 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
33 | Locked | 41 | 10.2 | 2441246609 | 4 |
0 | 49600000 | 48.8 | 5120 | QAM 64 | 1 |
1 | 43100000 | 48.8 | 5120 | QAM 64 | 2 |
2 | 36600000 | 48.8 | 5120 | QAM 64 | 3 |
3 | 30100000 | 48.8 | 5120 | QAM 64 | 4 |
4 | 23600000 | 48.8 | 5120 | QAM 64 | 5 |
3.0 Upstream 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 |
3.1 Upstream channels
6 | 11 | 44.2 | 2K | QAM 256 |
3.1 Upstream channels
6 | OFDMA | 220 | 74000000 | 18 | 0 |
03-12-2023 16:08:53 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
03-12-2023 09:46:27 | 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; |
02-12-2023 17:49:16 | 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; |
02-12-2023 11:26:23 | 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; |
02-12-2023 08:14:51 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-12-2023 08:14:51 | 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; |
02-12-2023 08:13:44 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
01-12-2023 23:17:08 | 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; |
01-12-2023 22:13:19 | 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; |
01-12-2023 21:09:29 | 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; |
01-12-2023 20:05:41 | 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; |
01-12-2023 07:19:56 | 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; |
01-12-2023 03:04:41 | 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; |
30-11-2023 21:45:37 | 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; |
30-11-2023 20:41:49 | 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; |
30-11-2023 19:38:00 | 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; |
30-11-2023 14:18:57 | 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; |
30-11-2023 12:11:19 | 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; |
30-11-2023 10:11:45 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
30-11-2023 10:11:41 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-11-2023 10:11:36 | 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; |
30-11-2023 10:11:29 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-11-2023 10:11:27 | notice | Honoring MDD; IP provisioning mode = IPv4 |
30-11-2023 10:11:10 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
30-11-2023 10:11:09 | critical | Cable Modem Reboot because of - unknown |
29-11-2023 09:04:46 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-11-2023 09:04:45 | critical | Cable Modem Reboot because of - unknown |
28-11-2023 09:25:40 | critical | Cable Modem Reboot because of - unknown |
28-11-2023 09:25:40 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-11-2023 08:53:40 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-11-2023 08:53:39 | critical | Cable Modem Reboot because of - unknown |
26-11-2023 19:26:07 | 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; |
on 05-12-2023 15:35
on 07-12-2023 16:11
Hi @Viper-t
Sorry to hear this is still unresolved for you.
I can see that my colleague Zach has supported you on your latest post to help further on your parents connection concerns.
If you respond to them they'll be able to assist further. Alternatively, you can post again on your original thread and one of the team will respond shortly. We ask that members do not create multiple threads on the same issue so we can keep all information clear within one area for all involved.
on 08-12-2023 17:13
Hi carley so I did post on my thread but virgin won't answer on there to my parents connection so I made a separate one, they do not answer for my problems either anymore. So do you want me to repost everything on my thread? As you can see its quite bad and has been for months for them. Below is my current connection and the settings page isn't loading again I think I'm on 5he latest firmware so do not know why it isn't loading. Can you tell me the curre.t firmware please to check.
Regards
on 08-12-2023 17:14
Sorry forgot to add
on 11-12-2023 09:37
Thanks for coming back to us Viper-t, if you post on your original post the team will get back to you as soon as they can. What happens, when you try to load the settings page? Which version of the firmware, are you currently on?
Kind Regards,
Steven_L
on 11-12-2023 18:47
Hey Steve I'm on fw: LG-RDK_6.9.35-2302.6 it loads properly now but didn't when I first got the hub 5 a week or so ago as you see above.
I'll try and get answers/help on my thread but it goes unanswered from time to time. My connection has been good since the last profile changes but its how long till they change me again. Thursday 7th till now good connection bqm nice 👍 no packet loss latency spikes, Qam on all upstream channels were dropped but today all at 64.
Regards