Virgin Media Community

[Cooparr]

Connection shows latency spikes and bursts of packet loss, the problem seems to appear then just disappear, becoming more frequent? 

Link to BQM from Saturday 23rd, as you can see the problem seems to resolve on its own. 

Saturday 23rd Graph 

Below is a link to a live BQM graph, showing that the problem has now returned. 

Live BQM graph 

Router Logs: 

Time Priority Description

25/05/2020 11:23:54	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 11:18:2	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 11:17:54	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 11:15:53	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:54:46	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:45:57	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:38:8	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:36:33	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:35:27	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:32:6	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:29:42	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 10:11:5	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 09:56:9	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 09:55:1	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 08:41:55	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 07:40:1	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 06:11:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 05:01:31	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 04:35:40	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/05/2020 04:29:10	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Cooparr]

Downstream bonded channels

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

1	187000000	-1.2	37	256 qam	7
2	195000000	-1.7	37	256 qam	8
3	203000000	-1.5	37	256 qam	9
4	211000000	-1.9	38	256 qam	10
5	219000000	-2	37	256 qam	11
6	227000000	-1.7	35	256 qam	12
7	235000000	-1.5	35	256 qam	13
8	243000000	-0.9	38	256 qam	14
9	251000000	-1.2	38	256 qam	15
10	259000000	-0.9	38	256 qam	16
11	267000000	-0.7	38	256 qam	17
12	275000000	-1	38	256 qam	18
13	283000000	0	38	256 qam	19
14	291000000	-0.4	38	256 qam	20
15	299000000	0	38	256 qam	21
16	307000000	0.4	39	256 qam	22
17	315000000	-0.5	38	256 qam	23
18	323000000	-0.2	38	256 qam	24
19	443000000	-1.7	38	256 qam	25
20	451000000	-1.5	38	256 qam	26
21	459000000	-1.2	38	256 qam	27
22	467000000	-1.7	38	256 qam	28
23	475000000	-1.7	38	256 qam	29
24	483000000	-1.5	38	256 qam	30

Downstream bonded channels

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

1	Locked	37.9	29398858	10761209
2	Locked	37.9	7737314	1727713
3	Locked	37.9	5317787	1045960
4	Locked	38.9	343320	52812
5	Locked	37.9	1150266	95934
6	Locked	35.7	7527283	1636813
7	Locked	35.7	7346326	1627039
8	Locked	38.6	924604	243680
9	Locked	38.9	233249	223646
10	Locked	38.9	2761990	375256
11	Locked	38.9	7627087	1587232
12	Locked	38.9	6063115	602327
13	Locked	38.9	439711	34142
14	Locked	38.9	1004882	12899
15	Locked	38.9	5595982	434411
16	Locked	39.3	3246037	164384
17	Locked	38.9	161689	691
18	Locked	38.9	931376	2483
19	Locked	38.9	137	0
20	Locked	38.9	144	0
21	Locked	38.9	89	0
22	Locked	38.9	51	0
23	Locked	38.9	66	0
24	Locked	38.9	80	0

Upstream bonded channels

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

1	53700073	5.1	5120	64 qam	2
2	60299975	5.1	5120	64 qam	1
3	39400000	5.1	5120	64 qam	4
4	46200038	5.1	5120	64 qam	3

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

[gary_dexter]

Upstream levels are too high and there’s a high RS count on your downstream.

Unless there’s an area fault you’ll need an engineer visit 

[Cooparr]

Thanks for the quick reply. 

What should my upstream levels be roughly? From checking and running the VM tests it showed no area faults. 

[Emily_G]

Thank you for the post Cooparr.

As the helpful @gary_dexter has explained the power levels do look on the high side.

I'll pop you over a private message now with some security questions if you could please confirm these so we can book in an appointment for you. You can respond to this by going to the purple envelope in the top right of your screen.

Thank you, Emily.