cancel
Showing results for 
Search instead for 
Did you mean: 

Another SNR issue, 3rd within 1 year?

Icantcrabhere
Superfast

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

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1539000000-1.438256 qam17
24110000001.240256 qam1
3419000000140256 qam2
44270000000.740256 qam3
54350000000.440256 qam4
64430000000.240256 qam5
7451000000040256 qam6
8459000000040256 qam7
9467000000040256 qam8
10475000000040256 qam9
11483000000-0.240256 qam10
12491000000-0.438256 qam11
13499000000-0.738256 qam12
14507000000-0.740256 qam13
15515000000-0.740256 qam14
16523000000-138256 qam15
17531000000-140256 qam16
18547000000-1.738256 qam18
19555000000-1.738256 qam19
20563000000-1.738256 qam20
21571000000-2.238256 qam21
22579000000-2.438256 qam22
23587000000-2.238256 qam23
24595000000-2.238256 qam24



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.62440
2Locked40.3770
3Locked40.3610
4Locked40.3700
5Locked40.3340
6Locked40.9350
7Locked40.3850
8Locked40.3850
9Locked40.3480
10Locked40.31010
11Locked40.3450
12Locked38.9840
13Locked38.92410
14Locked40.3880
15Locked40.3790
16Locked38.9690
17Locked40.3950
18Locked38.9990
19Locked38.9720
20Locked38.92560
21Locked38.91680
22Locked38.91180
23Locked38.61220
24Locked38.61510

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14620000041.3512064 qam1
23940000041512016 qam2
33260005440.5512016 qam3
42579998640.2512016 qam4



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0010
3ATDMA0010
4ATDMA0020
13 REPLIES 13

Icantcrabhere
Superfast

Network Log

Time Priority Description

17/05/2022 10:26:44ErrorDHCP 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:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/05/2022 22:26:44ErrorDHCP 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:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/05/2022 10:26:44ErrorDHCP 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:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2022 22:21:57ErrorDHCP 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:55ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2022 21:34:52Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 14:25:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2022 23:43:32ErrorDHCP 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:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/04/2022 03:51:37ErrorDHCP 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:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/04/2022 01:05:34noticeSW download Successful - Via NMS
26/04/2022 01:04:8noticeSW Download INIT - Via NMS
23/04/2022 06:35:37ErrorDHCP 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:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/04/2022 18:35:36ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

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!

Serena_C
Forum Team (Retired)
Forum Team (Retired)

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

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.

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.

 

Here to help 🙂
Virgin Media Forums Agent
Carley

jbrennand
Very Insightful Person
Very Insightful Person
Oh dear.... the dreaded "overutilisation".

See this thread on that issue and Andrew’s comments in Message 20

https://community.virginmedia.com/t5/Networking-and-WiFi/Internet-keeps-dropping-for-several-minutes...

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

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.


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.

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 🙂