Virgin Media Community

[mholland90]

Hey folks, 

Can someone look at my router stats to see if anything looks out of place. Been having multiple daily connection drops for a while now.

BQM (big red block is normal, hub sometimes stops responding to WAN pings): 

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

 

Downstream bonded channels

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

1	203000000	4	40	256 qam	9
2	211000000	4.3	40	256 qam	10
3	219000000	4.1	40	256 qam	11
4	227000000	4.1	40	256 qam	12
5	235000000	4	40	256 qam	13
6	243000000	4.1	40	256 qam	14
7	251000000	4.3	40	256 qam	15
8	259000000	4.5	40	256 qam	16
9	267000000	4.6	40	256 qam	17
10	275000000	4.8	40	256 qam	18
11	283000000	4.5	40	256 qam	19
12	291000000	4.5	40	256 qam	20
13	299000000	4.1	40	256 qam	21
14	307000000	4.5	40	256 qam	22
15	315000000	4.5	40	256 qam	23
16	323000000	5	40	256 qam	24
17	331000000	5.1	40	256 qam	25
18	339000000	5.4	40	256 qam	26
19	347000000	5	40	256 qam	27
20	355000000	5	40	256 qam	28
21	363000000	5	40	256 qam	29
22	371000000	5	40	256 qam	30
23	379000000	5	40	256 qam	31
24	387000000	5	40	256 qam	32

Downstream bonded channels

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

1	Locked	40.3	9	0
2	Locked	40.3	5	0
3	Locked	40.3	10	0
4	Locked	40.3	11	0
5	Locked	40.3	16	0
6	Locked	40.3	7	0
7	Locked	40.3	6	0
8	Locked	40.3	8	0
9	Locked	40.3	8	0
10	Locked	40.3	11	0
11	Locked	40.3	5	0
12	Locked	40.3	16	0
13	Locked	40.3	6	0
14	Locked	40.9	6	0
15	Locked	40.3	8	0
16	Locked	40.3	9	0
17	Locked	40.3	14	0
18	Locked	40.3	9	0
19	Locked	40.9	10	0
20	Locked	40.9	8	0
21	Locked	40.3	6	0
22	Locked	40.3	7	0
23	Locked	40.3	18	0
24	Locked	40.3	5	0

[mholland90]

Upstream bonded channels

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

1	60300000	43.8	5120	64 qam	1
2	39400000	43	5120	64 qam	4
3	46200000	43.3	5120	64 qam	3
4	53700000	43.5	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

Network Log

Time Priority Description

30/05/2022 13:35:23	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/05/2022 10:06:49	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/05/2022 10:06:47	Error	DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/05/2022 05:55:14	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/05/2022 18:51:4	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 05:43:21	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/05/2022 16:01:52	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 08:47:51	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/05/2022 21:48:20	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:38	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 14:08:12	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:42:42	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:42:42	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:42:42	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:42:41	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:39:1	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:39:1	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:38:59	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:38:59	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 12:37:13	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Anonymous]

Stats generally look okay to me but the BQM is awful. 

Have you checked the service status page on the website and ensured that all your cables are connections are tight and secure and not kinked? 

[mholland90]

Checked all cabling in my house and it does look fine.

The service status says everything is fine and the test thing has been stuck at this for months:

Looks like you've made a change to your package

You might find your service has a few interruptions while we sort things for you, so hold tight and give it a little while.

(No changes have been made to my package, always been on 200)

[Tudor]

Don’t use the website to check on service status, use this:

Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level.

[mholland90]

Just checked that and is said there were no faults in the area

[Anonymous]

Sadly it could possibly be local network congestion for which there are no instant fixes. The VM forum team might be able to double check this for you. 

There is a lively thread on this here https://community.virginmedia.com/t5/QuickStart-set-up-and/problem-with-latency-driving-me-crazy-ple...

[mholland90]

Had some more drops last night and this morning/early afternoon.

Decided on a whim to swap the cable over with the cable I had from when I had a V6 box, and so far no drops. Fingers crossed

[Ryan_N]

Hi mholland90, 

Thank you for your post. 

Sorry to hear of the issues you've been having here - also, thank you for posting the information you have done, it really helps us and the other members of the community. It's good to hear that you've had no drops since making the change - how has that been going over the last couple of days? 

Cheers, 

Ryan. 

[mholland90]

Since changing the cable it hasnt dropped at all. Im guessing then it was the cable that was the problem