SNR issue, again.

[Icantcrabhere]

Previously had an SNR issue in December which was fixed.
Seems to be back again after an issue in my area yesterday. (Hemel Hempstead, HP2)

Fault checker isn't showing issues currently, however it did yesterday.

Posting stats just because it's the normal thing to do,
Hub3, modem mode, the usual. - all wired.

I should note: the T3 error count on channel 4 is historical from the previous SNR issue.

Looks like this needs to be fixed, again.
QAM is all over the place, not amused.

Downstream bonded channels

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

1	539000000	-0.7	38	256 qam	17
2	411000000	1.7	40	256 qam	1
3	419000000	1.5	40	256 qam	2
4	427000000	1.2	40	256 qam	3
5	435000000	0.7	40	256 qam	4
6	443000000	0.5	40	256 qam	5
7	451000000	0.5	40	256 qam	6
8	459000000	0.5	40	256 qam	7
9	467000000	0.5	40	256 qam	8
10	475000000	0.4	40	256 qam	9
11	483000000	0.2	38	256 qam	10
12	491000000	0	38	256 qam	11
13	499000000	-0.2	40	256 qam	12
14	507000000	-0.2	40	256 qam	13
15	515000000	-0.2	40	256 qam	14
16	523000000	-0.5	40	256 qam	15
17	531000000	-0.5	40	256 qam	16
18	547000000	-1.2	38	256 qam	18
19	555000000	-1.2	40	256 qam	19
20	563000000	-1.2	38	256 qam	20
21	571000000	-1.5	38	256 qam	21
22	579000000	-1.7	38	256 qam	22
23	587000000	-1.7	38	256 qam	23
24	595000000	-1.5	38	256 qam	24

Downstream bonded channels

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

1	Locked	38.9	921	0
2	Locked	40.3	374	0
3	Locked	40.3	384	0
4	Locked	40.3	299	0
5	Locked	40.3	176	0
6	Locked	40.3	246	0
7	Locked	40.9	505	0
8	Locked	40.3	391	0
9	Locked	40.3	271	0
10	Locked	40.3	423	0
11	Locked	38.9	257	0
12	Locked	38.9	410	0
13	Locked	38.9	717	0
14	Locked	40.9	267	0
15	Locked	40.3	381	0
16	Locked	40.3	350	0
17	Locked	40.3	450	0
18	Locked	38.9	517	0
19	Locked	40.3	536	0
20	Locked	38.9	1443	0
21	Locked	38.6	761	0
22	Locked	38.9	718	0
23	Locked	38.6	779	0
24	Locked	38.9	959	0

Upstream bonded channels

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

1	46200263	44.5	5120	32 qam	1
2	32600000	44	5120	16 qam	3
3	39400039	44.3	5120	64 qam	2
4	25800126	43.3	5120	32 qam	4

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	4	0
2	ATDMA	0	0	3	0
3	ATDMA	0	0	4	0
4	ATDMA	0	0	9830	0

[Icantcrabhere]

Network Log

Time Priority Description

30/01/2022 19:03:19	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2022 23:39:52	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2022 07:03:18	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2022 19:47:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2022 19:03:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/01/2022 01:53:18	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/01/2022 07:03:16	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2022 10:30:54	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2022 06:03:16	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2022 03:02:59	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/01/2022 05:33:16	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 05:07:25	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/01/2022 17:33:15	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2021 09:04:36	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/12/2021 05:33:14	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/12/2021 20:54:45	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/12/2021 17:33:13	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 20:12:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/12/2021 05:33:13	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/12/2021 08:37:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Would be fantastic if we can have this truly ironed out,
SNR issues aren't the most fun thing to deal with, sadly.

More than happy to reply/PM with any additional info.

[Tudor]

Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page http://www.virginmedia.com/servicechecker

If no faults found:

Call Customer Services on 0345 454 1111/150 if you have a VM landline or wait a day or two for a VM staff member to get to your post.

[Icantcrabhere]

Sadly isn't showing up on Area faults when calling in, nor on the online checker currently.

Guess I'll have to wait and see!
hopefully the connection holds up! fingers crossed! 🙂

Going to put my stats after a fresh hub restart:

Upstream bonded channels

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

1	46200000	44.5	5120	32 qam	1
2	32600000	43.8	5120	16 qam	3
3	39400000	44.3	5120	64 qam	2
4	25800000	43.3	5120	32 qam	4

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

[Icantcrabhere]

Bump, since I seem to have been skipped over.
Packet loss appearing on my graph as of 11 ~ 11:30PM ish on 4th March.

Snapshot:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/fad71f69f760b30487772557a55fce5e88...

Live:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/3f9a0c6eff35d57ae0f42e221bb1b8b92039be2d

 
I'll post my stats up, again.
Large amounts of PRE-RS on certain channels.

Downstream bonded channels

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

1	539000000	-0.7	40	256 qam	17
2	411000000	1.7	40	256 qam	1
3	419000000	1.5	40	256 qam	2
4	427000000	1.4	40	256 qam	3
5	435000000	0.9	40	256 qam	4
6	443000000	0.7	40	256 qam	5
7	451000000	0.7	40	256 qam	6
8	459000000	0.7	40	256 qam	7
9	467000000	0.5	40	256 qam	8
10	475000000	0.5	40	256 qam	9
11	483000000	0.2	40	256 qam	10
12	491000000	0.2	38	256 qam	11
13	499000000	0	40	256 qam	12
14	507000000	-0.2	40	256 qam	13
15	515000000	0	40	256 qam	14
16	523000000	-0.2	40	256 qam	15
17	531000000	-0.4	40	256 qam	16
18	547000000	-1	38	256 qam	18
19	555000000	-1	40	256 qam	19
20	563000000	-1	38	256 qam	20
21	571000000	-1.4	38	256 qam	21
22	579000000	-1.5	38	256 qam	22
23	587000000	-1.5	38	256 qam	23
24	595000000	-1.4	38	256 qam	24

Downstream bonded channels

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

1	Locked	40.3	841	0
2	Locked	40.3	254	0
3	Locked	40.3	242	0
4	Locked	40.3	217	0
5	Locked	40.9	132	0
6	Locked	40.3	157	0
7	Locked	40.9	433	0
8	Locked	40.3	232	0
9	Locked	40.3	186	0
10	Locked	40.3	340	0
11	Locked	39.3	266	0
12	Locked	38.9	292	0
13	Locked	40.3	808	0
14	Locked	40.3	247	0
15	Locked	40.3	325	0
16	Locked	40.3	320	0
17	Locked	40.3	477	0
18	Locked	38.6	541	0
19	Locked	40.3	546	0
20	Locked	38.6	1087	0
21	Locked	38.9	2066	0
22	Locked	38.9	2429	0
23	Locked	38.6	81895	0
24	Locked	38.9	487775	0

Upstream bonded channels

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

1	46200000	45	5120	64 qam	1
2	32600000	44	5120	64 qam	3
3	39400000	44.5	5120	64 qam	2
4	25800000	43.8	5120	32 qam	4

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	5	0
2	ATDMA	0	0	1	0
3	ATDMA	0	0	5	0
4	ATDMA	0	0	4	0

[Icantcrabhere]

General Configuration

Network access	Allowed
Maximum Number of CPEs	1
Baseline Privacy	Enabled
DOCSIS Mode	Docsis30
Config file	cmreg-vmdg505-bbt057-b.cm

Primary Downstream Service Flow

SFID	276018
Max Traffic Rate	117000047
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	276017
Max Traffic Rate	10500047
Max Traffic Burst	16320
Min Traffic Rate	0
Max Concatenated Burst	16320
Scheduling Type	BestEffort

Refresh data

Network Log

Time Priority Description

28/02/2022 07:49:46	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/02/2022 16:18:23	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/02/2022 19:49:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2022 08:36:34	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/02/2022 07:49:44	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/02/2022 20:17:45	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2022 19:49:43	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2022 01:59:34	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2022 07:49:42	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/02/2022 17:32:30	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2022 19:49:41	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2022 14:23:11	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2022 07:36:13	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2022 07:09:27	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2022 19:03:19	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2022 23:39:52	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2022 07:03:18	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2022 19:47:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2022 19:03:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/01/2022 01:53:18	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

As you can see, Huge PRE-RS errors on Channel 23 + 24 with packet loss on the TBB graph,
the PRE-RS only climbed when the packet loss started.

Also noticed channels on 2 + 4 on the upstream still dropping back to 32QAM.

[Icantcrabhere]

Made a previous post, been accidentally skipped for the past month or so.
Can this be flagged for the mods/staff.
https://community.virginmedia.com/t5/Networking-and-WiFi/SNR-issue-again/m-p/4958043#M464484

Unfortunately the connection is now looking the most terrible it has been for a while.

Snapshot from yesterday:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/fad71f69f760b30487772557a55fce5e88...

Live:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/3f9a0c6eff35d57ae0f42e221bb1b8b92039be2d

Stats from yesterday can be seen in the thread I linked at the top of this post.
However all upstream channels are now jumping around, often staying at 16QAM for long amounts of time.

Please help me out if you can!

[Martin_N]

Hi Icantcrabhere,

Thank you for your post. We're sorry to hear you're still having issues with your broadband service. 

I have taken a look on our system and I have seen some errors that would require an engineer to resolve. 

I have booked a visit in for you. Please check your online account for the details regarding the visit. 

^Martin

[Icantcrabhere]

Hi there,

Technician has been and agreed about potential noise being let in on the network, but not from my home.
Apparently he had talked to colleagues about it, prior to the visit. -  but I need this verified.
So as of yet we obviously have no resolution.

He showed me something on his phone,
Wondering if you could inform me further about the following reference number:  F009688492
This is what he showed me, however I'd like to make sure it it 100% correct.

Has a "Date opened" of March 8th, 12:33,
Estimated end date: 15th march 12:35.
Priority: P4

Get back in touch when you can, thanks!

[David_Bn]

Good Afternoon @Icantcrabhere, 

I've been able to look into your local area, and it appears that the outage is showing as an end time of 18:00 today

Please update us beyond this time frame to let us know how the services are performing

Kindest regards,

David_Bn