Virgin Media Community

[footinfront]

Could anyone please advise as to why i am getting high latency?  it gets that bad i have to do soft restart of hub and hard reset of hub. take a look at todays graph.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/cec12f45aad22d1fa0afa5cc12d4cc9bc9b6ab7a-17-05-2022

 if martin is around please help out. Thanks

[jbrennand]

That is poor..... Post up all of the Hub data.

[footinfront]

thanks john for the reply, i'll post hub status. down stream=

1	330750000	0.7	38	256 qam	25
2	266750000	1.2	38	256 qam	17
3	274750000	1	38	256 qam	18
4	282750000	0.7	38	256 qam	19
5	290750000	0.5	38	256 qam	20
6	298750000	0.5	37	256 qam	21
7	306750000	0.7	38	256 qam	22
8	314750000	0.5	38	256 qam	23
9	322750000	0.5	38	256 qam	24
10	338750000	0.2	37	256 qam	26
11	346750000	0.5	38	256 qam	27
12	354750000	0.2	38	256 qam	28
13	362750000	0.2	38	256 qam	29
14	370750000	-0.2	37	256 qam	30
15	378750000	-0.7	37	256 qam	31
16	386750000	-1.2	37	256 qam	32
17	394750000	-1.4	37	256 qam	33
18	402750000	-1.5	37	256 qam	34
19	410750000	-1.7	37	256 qam	35
20	418750000	-1.9	37	256 qam	36
21	522750000	-2.9	37	256 qam	37
22	530750000	-3	37	256 qam	38
23	538750000	-3.4	37	256 qam	39
24	546750000	-3.5	37	256 qam	40

Downstream bonded channels

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

1	Locked	38.6	354	0
2	Locked	38.6	689	0
3	Locked	38.6	644	0
4	Locked	38.6	601	0
5	Locked	38.9	581	0
6	Locked	37.6	526	0
7	Locked	38.6	481	0
8	Locked	38.9	437	0
9	Locked	38.6	413	0
10	Locked	37.3	331	0
11	Locked	38.6	303	0
12	Locked	38.9	280	0
13	Locked	38.6	254	0
14	Locked	37.6	235	0
15	Locked	37.3	228	0
16	Locked	37.6	226	0
17	Locked	37.3	231	0
18	Locked	37.6	216	0
19	Locked	37.3	250	0
20	Locked	37.6	217	0
21	Locked	37.6	121	0
22	Locked	37.6	115	0
23	Locked	37.3	121	0
24	Locked	37.6	119

[footinfront]

Refresh data

Upstream bonded channels

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

1	53700131	42.5	5120	64 qam	1
2	46199946	41.8	5120	64 qam	2
3	39399934	41.8	5120	64 qam	3
4	32600070	41.8	5120	64 qam	4

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	0	0

[footinfront]

Refresh data

Network Log

Time Priority Description

18/05/2022 17:45:47	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2022 15:45:25	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2022 15:43:45	notice	NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2022 15:39:59	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2022 15:38:18	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2022 15:28:33	notice	NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2022 15:18:37	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/05/2022 15:13:3	notice	NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2022 06:14:13	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/05/2022 06:13:38	critical	TFTP Request Retries exceeded, CM unable to register
16/05/2022 06:13:38	critical	TFTP failed - Request sent - No Response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2022 21:46:1	critical	TFTP Request Retries exceeded, CM unable to register
15/05/2022 21:46:1	critical	TFTP failed - Request sent - No Response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2022 21:45:14	notice	NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2022 21:34:35	critical	TFTP Request Retries exceeded, CM unable to register
15/05/2022 21:34:34	critical	TFTP failed - Request sent - No Response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2022 21:26:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2022 21:24:44	critical	TFTP Request Retries exceeded, CM unable to register
15/05/2022 21:24:43	critical	TFTP failed - Request sent - No Response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2022 21:16:3	notice	NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[footinfront]

also a graph of todays monitor. note added, has anyone from virgin finally tightened that lose screw? hope it lasts.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/f97a38e0354fe0cb9df583d53765a393a7e289dc-18-05-2022

Congratulations to the engineers.

[jbrennand]

Stats look fine - logs need someone more experienced than me to interpret.

Whilst waiting, is the Hub in normal router mode or have you got it in modem mode with your own router ?

And what equipment have you got plugged into the Hub on ethernet cables?

There have been a few recent threads where that other equipment was the source of theissue.

[footinfront]

hello hub is in normal mode and i have one connection to a  tp link and one ethernet to a xbox one ( not powered up atm ). did you check my graph for today?

[footinfront]

tp link is used for cctv.

[jbrennand]

Looks a lot better today - but still not perfect - what is performance like today?

If it goes pear shaped again try this. Disconnect the two other devices etherney=t connections and leave a few hours - overnight ? Then next day see what the S+BQM is like. If its has cleared up - plug one device back in for a few hours and see what happens. Then add the second connection and see what happens on the BQM