Menu
Reply
Highlighted
  • 92
  • 1
  • 11
Dialled in
554 Views
Message 1 of 3
Flag for a moderator

Chasing up on an old packet loss problem.

Hey,
So I made previous posts about packet loss.
Unfortunately after some technician visits, one of which suggested I get in touch with the area manager.
The technician was actually said he realistically wouldn't be able to do anything from this end and that swapping the hub and more pinhole resets would be pointless.

A forum staff member messaged our area manager, to get in touch with me(?), unfortunately the manager never did. (I can provide PM's to a staff member, if needed)

I've been very tight on time till lately, due to some personal real life problems(isn't depression super fun? aha), so I've only just had chance to once again chase this up now that I'm back on my feet. 🙂

(Superhub 3, modem mode, ethernet cable)

Graph from today(12/11/2020):
https://www.thinkbroadband.com/broadband/monitoring/quality/share/7ebbda72e5d854dc08a29e0c9e9742b5d9...
The packet loss just before the reboot and just after just appeared for no reason.
Usually the lost is most noticeable when watching videos/downloading(Game updates, anything download actually)


Live graph for future use:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/3f9a0c6eff35d57ae0f42e221bb1b8b920...

I can provide graphs for previous days as well, if required or wanted.
I will post up modem logs/power levels etc,
although they should all be very much in line, as before.

Downstream bonded channels

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

15310000003.440256 qam16
25230000003.540256 qam15
35390000003.540256 qam17
45470000003.940256 qam18
5555000000440256 qam19
65630000003.540256 qam20
75710000002.740256 qam21
8579000000240256 qam22
95870000002.240256 qam23
105950000002.940256 qam24
116030000003.240256 qam25
126110000003.440256 qam26
136190000002.740256 qam27
146270000002.740256 qam28
156350000002.740256 qam29
166430000003.240256 qam30
176510000003.540256 qam31
186590000003.240256 qam32
19667000000340256 qam33
20675000000340256 qam34
21683000000340256 qam35
226910000003.740256 qam36
236990000003.740256 qam37
247070000003.540256 qam38

 

ownstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked40.3120
2Locked40.950
3Locked40.950
4Locked40.350
5Locked40.940
6Locked40.950
7Locked40.300
8Locked40.300
9Locked40.300
10Locked40.350
11Locked40.350
12Locked40.950
13Locked40.940
14Locked40.900
15Locked40.340
16Locked40.340
17Locked40.950
18Locked40.300
19Locked40.300
20Locked40.300
21Locked40.310
22Locked40.9190
23Locked40.350
24Locked40.900



0 Kudos
Reply
Highlighted
  • 92
  • 1
  • 11
Dialled in
550 Views
Message 2 of 3
Flag for a moderator

Re: Chasing up on an old packet loss problem.

Upstream bonded channels

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

12580000040.8512064 qam4
24620000042.3512064 qam1
33940022441.8512064 qam2
43260000041.3512064 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Network Log

Time Priority Description

12/11/2020 07:14:0ErrorDHCP RENEW WARNING - Field invalid in response v4 option;
10/11/2020 05:17:19criticalNo Ranging Response received - T3 time-out;
08/11/2020 19:38:49ErrorDHCP RENEW WARNING - Field invalid in response v4 option;
05/11/2020 09:28:24criticalNo Ranging Response received - T3 time-out;CM-
05/11/2020 09:27:25criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
05/11/2020 09:21:30Warning!Lost MDD Timeout;
05/11/2020 09:21:26Warning!RCS Partial Service
05/11/2020 09:21:26criticalSYNC Timing Synchronization failure - Loss of Sync;
05/11/2020 09:21:26Warning!RCS Partial Service;
05/11/2020 09:21:26criticalSYNC Timing Synchronization failure - Loss of Sync;
29/10/2020 05:49:12ErrorDHCP RENEW WARNING - Field invalid in response v4 option;
26/10/2020 02:21:35criticalNo Ranging Response received - T3 time-out;CM-
25/10/2020 21:29:33ErrorDHCP RENEW WARNING - Field invalid in response v4 option
01/01/1970 00:01:43criticalNo Ranging Response received - T3 time-out;CM-
22/10/2020 01:35:25noticeSW download Successful - Via NMS
22/10/2020 01:30:17noticeSW Download INIT - Via NMS
22/10/2020 01:09:4ErrorDHCP RENEW WARNING - Field invalid in response v4 option;=
19/10/2020 10:10:34criticalNo Ranging Response received - T3 time-out;CM-
18/10/2020 13:09:4ErrorDHCP RENEW WARNING - Field invalid in response v4 option;
16/10/2020 18:35:32criticalNo Ranging Response received - T3 time-out;CM-


Removed MAC Address from tables, etc - hence shortened errors

Also took a screenshot from a few ago(for when I could post again), of all upstream channels dropping to 32QAM.
Will be here after being approved.32 badness.png32 badness.png
It drops to lower QAM on different channels every now and then, but I had never seen them all go at the same time till this picture.

Only other thing that worries me,
is the "Partial service" > T4

Had this happen a few times in more recent months.

0 Kudos
Reply
Highlighted
  • 92
  • 1
  • 11
Dialled in
186 Views
Message 3 of 3
Flag for a moderator

Re: Chasing up on an old packet loss problem.

Hey again,
Been around 8 days since I've posted - not sure If the staff have just been unusually busy (it's understandable in these times), or if maybe the thread accidently got looked over(Also understandable)

Things seem to be getting a little worse with the connection, noticing some lovely T3 errors cropping up now,
Watching videos/streams or updating things is still causing major packet loss as well. (Worse than before infact)

I'll add some pictures, will have to wait to be approved however.
The think broadband picture was from yesterday, when updating a game.
wow update packet loss.pngt3 errors popping up.png

Link to my live graph is in the first post of the thread.


I can repost all my stats again if needed, although it doesn't seem much has changed since the original post (other than the T3's)

0 Kudos
Reply