Virgin Media Community

[expatista]

Hi,  Apart from my wifi issues, I am having intermittent connectivity and slow internet speeds over a wired connection as well.   I switched to wired while I wait for 3rd party wifi equipment.  I am posting the network log from the hub below.  Wondering if there is any insight in the log such as the critical errors?

Time Priority Description

25/01/2021 12:02:47	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/01/2021 07:10:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 15:55:33	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 15:55:33	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 14:00:2	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 14:00:2	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 11:22:50	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 11:22:50	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 11:03:57	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 11:03:57	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:33:25	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:33:24	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:23:54	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:23:54	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:19:39	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:19:39	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 06:47:16	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 06:47:16	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 06:47:15	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 06:47:15	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[expatista]

Forgot to mention that download speed test range from 40-70Mbps upload speeds vary from 1-9Mbps.  I have the 100Mbps package.

[Adduxi · Accepted solution]

You should not have those SYNC errors.  Post your power levels for comment as there is something amiss with your circuit.

In the meantime, check all connections are tight as loose connections can cause noise ingress on the circuit.

[expatista]

Is that the downstream and upstream logs? Do I need to blank out any personal information before posting those logs? TIA Andrew

[Adduxi]

---

@expatista wrote:
Is that the downstream and upstream logs? Do I need to blank out any personal information before posting those logs? TIA Andrew

---

Just copy and paste the numbers into the post. Then ignore the warnings messages and the Board software will fix it before it posts.  There is nothing personal in the power level logs. 

[expatista]

BQM link

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

Downstream bonded channels

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

1	474250000	6.5	38	256 qam	9
2	482250000	6.5	38	256 qam	10
3	490250000	6.6	38	256 qam	11
4	498250000	6.4	38	256 qam	12
5	506250000	6	38	256 qam	13
6	514250000	6	38	256 qam	14
7	522250000	6.1	38	256 qam	15
8	530250000	6.1	38	256 qam	16
9	538250000	6.1	38	256 qam	17
10	546250000	6	38	256 qam	18
11	554250000	6.3	38	256 qam	19
12	562250000	6.5	38	256 qam	20
13	570250000	6.5	38	256 qam	21
14	578250000	6.5	38	256 qam	22
15	586250000	6.8	40	256 qam	23
16	594250000	6.1	38	256 qam	24
17	658250000	6	40	256 qam	25
18	666250000	6.5	38	256 qam	26
19	674250000	6.5	38	256 qam	27
20	682250000	6.6	38	256 qam	28
21	690250000	7	38	256 qam	29
22	698250000	6.8	38	256 qam	30
23	706250000	7	40	256 qam	31
24	714250000	7	38	256 qam	32

Downstream bonded channels

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

1	Locked	38.9	10	0
2	Locked	38.9	14	0
3	Locked	38.9	10	0
4	Locked	38.9	2	0
5	Locked	38.6	12	0
6	Locked	38.9	9	0
7	Locked	38.9	11	0
8	Locked	38.9	14	0
9	Locked	38.9	16	0
10	Locked	38.9	19	0
11	Locked	38.9	31	0
12	Locked	38.9	14	0
13	Locked	38.6	13	0
14	Locked	38.9	26	0
15	Locked	40.3	14	0
16	Locked	38.6	12	0
17	Locked	38.9	21	0
18	Locked	38.9	38	0
19	Locked	38.6	13	0
20	Locked	38.9	16	0
21	Locked	38.9	15	0
22	Locked	38.9	13	0
23	Locked	40.3	29	0
24	Locked	38.6	7	0

Upstream bonded channels

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

1	46200000	45.8	5120	64 qam	1
2	25799931	46.3	5120	64 qam	4
3	32600000	46.3	5120	64 qam	3
4	39400000	46	5120	64 qam	2

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

[Adduxi]

Nothing wrong with those power levels at the moment, and the PostRS errors are all zero. I'm assuming the Hub was reset just before the power levels were copied?   

The BQM is not populated enough as yet, so we will need to wait a while to comment.