Packet loss

[piggo64]

Had a field tech out last week. He changed the in line isolators and checked the levels .

It was fine for about 12 hours , then the latency spikes and packet loss returned.

BQM ; 

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

A lot of T3 timeouts:

3.0 Upstream channels

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

1	46200000	38.520599	5120 KSym/sec	64QAM	3
2	39400000	38.020599	5120 KSym/sec	64QAM	4
3	53700000	39.020599	5120 KSym/sec	64QAM	2
4	60300000	40.020599	5120 KSym/sec	64QAM	1

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	US_TYPE_STDMA	0	0	4	0
2	US_TYPE_STDMA	0	0	17	0
3	US_TYPE_STDMA	0	0	1	0
4	US_TYPE_STDMA	0	0	5	0

[jbrennand]

Post the Downstream data tables and the Network logs.

BQM does look iffy!

What equipment have you got connected to the Hub on ethernet cables?

[piggo64]

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status	Online	DOCSIS 3.1
Primary downstream channel	Locked	SC-QAM
DOCSIS 3.0 channels	31	4
DOCSIS 3.1 channels	1	0

Refresh data

3.0 Downstream channels

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

32	387000000	3.200001	38.983261	QAM256	32
33	395000000	3.200001	38.983261	QAM256	33
34	403000000	3.400002	38.983261	QAM256	34
35	411000000	3.299999	40.366287	QAM256	35
36	419000000	3.400002	40.366287	QAM256	36
6	179000000	5.400002	38.983261	QAM256	6
7	187000000	5.500000	38.983261	QAM256	7
8	195000000	5.400002	38.983261	QAM256	8
9	203000000	5.199997	38.983261	QAM256	9
10	211000000	5.000000	38.983261	QAM256	10
11	219000000	5.099998	38.983261	QAM256	11
12	227000000	4.900002	40.366287	QAM256	12
13	235000000	4.699997	38.983261	QAM256	13
14	243000000	4.400002	40.366287	QAM256	14
15	251000000	4.300003	38.983261	QAM256	15
16	259000000	3.900002	38.983261	QAM256	16
17	267000000	4.300003	40.366287	QAM256	17
18	275000000	4.400002	40.366287	QAM256	18
19	283000000	4.000000	40.946209	QAM256	19
20	291000000	3.900002	40.366287	QAM256	20
21	299000000	4.199997	40.366287	QAM256	21
22	307000000	4.500000	40.366287	QAM256	22
23	315000000	4.599998	40.946209	QAM256	23
24	323000000	4.699997	38.983261	QAM256	24
25	331000000	4.199997	38.983261	QAM256	25
26	339000000	4.199997	38.983261	QAM256	26
27	347000000	4.099998	40.366287	QAM256	27
28	355000000	4.400002	40.946209	QAM256	28
29	363000000	4.400002	40.366287	QAM256	29
30	371000000	4.099998	40.366287	QAM256	30
31	379000000	3.799999	38.983261	QAM256	31

3.0 Downstream channels

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

32	Locked	38.983261	0	0
33	Locked	38.983261	0	0
34	Locked	38.983261	0	0
35	Locked	40.366287	0	0
36	Locked	40.366287	0	0
6	Locked	38.983261	0	0
7	Locked	38.983261	0	0
8	Locked	38.983261	0	0
9	Locked	38.983261	0	0
10	Locked	38.983261	0	0
11	Locked	38.983261	0	0
12	Locked	40.366287	0	0
13	Locked	38.983261	0	0
14	Locked	40.366287	0	0
15	Locked	38.983261	0	0
16	Locked	38.983261	0	0
17	Locked	40.366287	0	0
18	Locked	40.366287	0	0
19	Locked	40.946209	0	0
20	Locked	40.366287	0	0
21	Locked	40.366287	0	0
22	Locked	40.366287	0	0
23	Locked	40.946209	0	0
24	Locked	38.983261	0	0
25	Locked	38.983261	0	0
26	Locked	38.983261	0	0
27	Locked	40.366287	0	0
28	Locked	40.946209	0	0
29	Locked	40.366287	0	0
30	Locked	40.366287	0	0
31	Locked	38.983261	0	0

 

It's odd that the network log is always blank.

I have 3 PC's  and a tv connected via ethernet , all CAT6 or higher

[jbrennand]

Can you try this experiment..

-----------------------------------------

There is one other option, there have been several threads on here recently where similar BQM latency/packet loss problems were eventually pinned down to a dodgy piece of connected kit affecting the connection . Bad connectors on ethernet cables and faulty network switches being high on the list of suspects

What I advised was... if you run the BQM for 24h to get a picture of the issues (you have done this) - and then unplug all the ethernet cable connections from the Hub and just let it run - overnight is best - then in the morning look at the BQM and see if it has cleaned up. If it has - plug the devices back in one at a time for an hour or two each until the problem reappears and that should indicate where to look for what is causing the issues

Examples.

See message 12 in the first and 13 in the second.
https://community.virginmedia.com/t5/Networking-and-WiFi/Internet-connection-dropping/td-p/4781287/p...
https://community.virginmedia.com/t5/Networking-and-WiFi/Intermittent-Connection/td-p/5069984/page/2

[piggo64]

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

[jbrennand]

This links to nothing