on 17-05-2022 13:34
Hi,
Seem to again have another potential SNR issue.
QAM is all over the place on the upstream.
Although irrelevant
Superhub 3, modem mode.
Live graph for when things are undoubtedly going to get worse:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/99d0211a42b0af7eea816fe43594835dbd170019
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 539000000 | -1.4 | 38 | 256 qam | 17 |
2 | 411000000 | 1.2 | 40 | 256 qam | 1 |
3 | 419000000 | 1 | 40 | 256 qam | 2 |
4 | 427000000 | 0.7 | 40 | 256 qam | 3 |
5 | 435000000 | 0.4 | 40 | 256 qam | 4 |
6 | 443000000 | 0.2 | 40 | 256 qam | 5 |
7 | 451000000 | 0 | 40 | 256 qam | 6 |
8 | 459000000 | 0 | 40 | 256 qam | 7 |
9 | 467000000 | 0 | 40 | 256 qam | 8 |
10 | 475000000 | 0 | 40 | 256 qam | 9 |
11 | 483000000 | -0.2 | 40 | 256 qam | 10 |
12 | 491000000 | -0.4 | 38 | 256 qam | 11 |
13 | 499000000 | -0.7 | 38 | 256 qam | 12 |
14 | 507000000 | -0.7 | 40 | 256 qam | 13 |
15 | 515000000 | -0.7 | 40 | 256 qam | 14 |
16 | 523000000 | -1 | 38 | 256 qam | 15 |
17 | 531000000 | -1 | 40 | 256 qam | 16 |
18 | 547000000 | -1.7 | 38 | 256 qam | 18 |
19 | 555000000 | -1.7 | 38 | 256 qam | 19 |
20 | 563000000 | -1.7 | 38 | 256 qam | 20 |
21 | 571000000 | -2.2 | 38 | 256 qam | 21 |
22 | 579000000 | -2.4 | 38 | 256 qam | 22 |
23 | 587000000 | -2.2 | 38 | 256 qam | 23 |
24 | 595000000 | -2.2 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 244 | 0 |
2 | Locked | 40.3 | 77 | 0 |
3 | Locked | 40.3 | 61 | 0 |
4 | Locked | 40.3 | 70 | 0 |
5 | Locked | 40.3 | 34 | 0 |
6 | Locked | 40.9 | 35 | 0 |
7 | Locked | 40.3 | 85 | 0 |
8 | Locked | 40.3 | 85 | 0 |
9 | Locked | 40.3 | 48 | 0 |
10 | Locked | 40.3 | 101 | 0 |
11 | Locked | 40.3 | 45 | 0 |
12 | Locked | 38.9 | 84 | 0 |
13 | Locked | 38.9 | 241 | 0 |
14 | Locked | 40.3 | 88 | 0 |
15 | Locked | 40.3 | 79 | 0 |
16 | Locked | 38.9 | 69 | 0 |
17 | Locked | 40.3 | 95 | 0 |
18 | Locked | 38.9 | 99 | 0 |
19 | Locked | 38.9 | 72 | 0 |
20 | Locked | 38.9 | 256 | 0 |
21 | Locked | 38.9 | 168 | 0 |
22 | Locked | 38.9 | 118 | 0 |
23 | Locked | 38.6 | 122 | 0 |
24 | Locked | 38.6 | 151 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 41.3 | 5120 | 64 qam | 1 |
2 | 39400000 | 41 | 5120 | 16 qam | 2 |
3 | 32600054 | 40.5 | 5120 | 16 qam | 3 |
4 | 25799986 | 40.2 | 5120 | 16 qam | 4 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
on 17-05-2022 13:35
Time Priority Description
17/05/2022 10:26:44 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2022 04:46:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/05/2022 22:26:44 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/05/2022 14:58:50 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/05/2022 10:26:44 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/05/2022 22:21:57 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/05/2022 22:21:55 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/05/2022 21:34:52 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2022 14:25:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/04/2022 23:43:32 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/04/2022 22:11:21 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/04/2022 03:51:37 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/04/2022 09:57:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/04/2022 01:05:34 | notice | SW download Successful - Via NMS |
26/04/2022 01:04:8 | notice | SW Download INIT - Via NMS |
23/04/2022 06:35:37 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/04/2022 05:26:31 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/04/2022 18:35:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 17-05-2022 13:36
As you can see:
3 upstream channels are pretty much sitting at the ever so dreadful 16QAM.
hopefully this can be looked into/solved before it gets as bad as it did before.
Cheers for the help!
on 19-05-2022 14:45
Hey Icantcrabhere, thank you for your post today and I am sorry to see there could be a potential SRN outage. I can understand your frustration.
I have had a look on our systems and I cannot see any outages / planned work at the moment. I can see the last SNR outages were in March 2022.
Please can you let me know what sort of connections you are experiencing is it just on modem mode? Have you tried retting it to see if that makes a different or tried it on the WIFI to see its improved? Thanks
on 19-05-2022 15:36
Hi Serena.
Firstly thank you for your reply, it's appreciated!
The connection uptime is fine,
however x3 channels on 16QAM for the past two days is not. - although they are currently at the correct modulation, such is the joy of SNR related issues, it can be very intermittent.
Although the last SNR issues were in March it was the exact same symptoms.
If this does indeed get flagged as an SNR issue down the line, which I suspect it will .. that will be the third time in the space of 12 months, unfortunately.
I have no issues with the connection remaining up. - Ethernet or WIFI.
Running the hub standalone or in Modem mode would not be an issue contributing to channels dropping Modulation.
I'll keep monitoring and updating.
on 21-05-2022 16:38
Hi @Icantcrabhere.
Sorry that this is still ongoing for you.
I have checked the area and can see more of evidence towards a High Utilisation issue than an SNR. We will also monitor this at our side, please keep up updated with any further issues and updates.
on 21-05-2022 16:48
on 21-05-2022 17:42
Hi Carley,
I was generally more worried about the 16QAM happening the other day, although it seems to have currently returned to normal.
Can you tell me the utilisation levels in my area? - since you guys obviously have a threshold of what you deem acceptable/unacceptable.
I will continue monitoring, however.
@jbrennand Unfortunately I'm far too aware of that curse, it's why I've told multiple friends locally that it's probably not wise for them to sign up with VM, aha!
Luckily (although a bit more spikey than I'd like):
https://www.thinkbroadband.com/broadband/monitoring/quality/share/99d0211a42b0af7eea816fe43594835dbd170019
My graph is better than most others I've seen, mine seems minor at most.
on 24-05-2022 08:50
Hi Icantcrabhere,
Thank you for reaching back out, I have had a look our end and cannot see any current issues, I can see you haven't rebooted the Router since the issue was present and it is still in Modem mode, please try a reboot.
Regards
Paul.
on 24-05-2022 14:43
Hi Paul,
Currently the Upstream modulation is as expected 🙂
I'll be sure to reboot the router when ASAP when it's not in use, although probably not of any use in the current situation: Protocol is protocol, however!
Is there any chance you could expand upon your colleagues admission of High utilisation, though? (a post or so up)
I'd love to know what my area is currently at in terms of utilisation, because although nowhere near as bad as others... my BQM is definitely somewhat unclean compared to what I'd like.
Many thanks 🙂