Menu
Reply
claum
  • 12
  • 0
  • 0
Joining in
286 Views
Message 1 of 12
Flag for a moderator

Gig1 Hub 4 packet loss

https://www.thinkbroadband.com/broadband/monitoring/quality/share/8cfa3b768939a742cfe589de368939e2fe6900b2-14-04-2021

That is my BQM. Only been monitoring for a few days but every days graph is similar to that one. The lag is noticeable on streams, games and probably everything else.

Speeds are fine. I get like 600-700 on wifi. 

 

tell me what other info you need

0 Kudos
Reply
lotharmat
  • 937
  • 70
  • 142
Well-informed
243 Views
Message 2 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

Can you post your Hub status and logs?
Someone should be spot if there is a problem
Navigate to http://192.168.0.1 (or http://192.168.100.1 - if in modem mode)
Don't log in!
Click on 'router status'
Copy/paste the data from each of the tabs. The forum software will remove the MAC addresses for you (you may need to click the 'post' button again).

There may be noise on the line or poor power levels causing the modem to keep messing about getting synchronised



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

0 Kudos
Reply
claum
  • 12
  • 0
  • 0
Joining in
219 Views
Message 3 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

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
0 Kudos
Reply
claum
  • 12
  • 0
  • 0
Joining in
218 Views
Message 4 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

3.0 Downstream channels

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

253310000004.30000338.983261QAM25625
323870000003.59999840.366287QAM25632
333950000003.50000038.983261QAM25633
344030000003.59999840.366287QAM25634
41630000003.20000140.946209QAM2564
51710000003.79999940.946209QAM2565
61790000004.50000040.366287QAM2566
71870000004.90000240.946209QAM2567
81950000004.80000340.366287QAM2568
92030000004.59999840.366287QAM2569
102110000004.80000340.366287QAM25610
112190000004.59999840.366287QAM25611
122270000004.80000340.366287QAM25612
132350000004.90000240.366287QAM25613
142430000004.90000240.366287QAM25614
152510000005.00000040.366287QAM25615
162590000005.09999840.946209QAM25616
172670000004.90000240.366287QAM25617
182750000004.59999840.366287QAM25618
192830000003.90000240.366287QAM25619
202910000004.09999840.366287QAM25620
212990000004.50000040.366287QAM25621
223070000004.50000040.366287QAM25622
233150000004.69999740.366287QAM25623
243230000004.59999838.983261QAM25624
263390000004.40000240.366287QAM25626
273470000004.09999840.366287QAM25627
283550000004.00000040.366287QAM25628
293630000004.19999740.366287QAM25629
303710000003.59999840.366287QAM25630
313790000003.59999840.366287QAM25631



3.0 Downstream channels

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

25Locked38.98326100
32Locked40.36628700
33Locked38.98326100
34Locked40.36628700
4Locked40.94620900
5Locked40.94620900
6Locked40.36628700
7Locked40.94620900
8Locked40.36628700
9Locked40.36628700
10Locked40.36628700
11Locked40.36628700
12Locked40.36628700
13Locked40.36628700
14Locked40.36628700
15Locked40.36628700
16Locked40.94620900
17Locked40.36628700
18Locked40.36628700
19Locked40.36628700
20Locked40.36628700
21Locked40.36628700
22Locked40.36628700
23Locked40.36628700
24Locked38.98326100
26Locked40.36628700
27Locked40.36628700
28Locked40.36628700
29Locked40.36628700
30Locked40.36628700
31Locked40.36628700



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1880QAM256759


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked41-1.022522237126
0 Kudos
Reply
claum
  • 12
  • 0
  • 0
Joining in
216 Views
Message 5 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

3.0 Upstream channels

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

13940000044.2705995120 KSym/sec64QAM4
23260000044.2705995120 KSym/sec64QAM5
34620000044.2705995120 KSym/sec64QAM3
45370000042.2705995120 KSym/sec64QAM2



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
0 Kudos
Reply
claum
  • 12
  • 0
  • 0
Joining in
215 Views
Message 6 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

General Configuration

Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
wrkldJKDHSUBsgvca69834ncx



Primary Downstream Service Flow

SFID
24640
Max Traffic Rate
1200000450
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow

SFID
24639
Max Traffic Rate
55000270
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
16320
Scheduling Type
bestEffort
0 Kudos
Reply
claum
  • 12
  • 0
  • 0
Joining in
214 Views
Message 7 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

Network Log

Time Priority Description

Sat Apr 10 12:43:53 20215DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 06:23:34 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 07:24:39 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 07:25:28 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 3; New Profile: 4.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 07:25:29 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 08:46:09 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 2; New Profile: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 08:46:09 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 10:37:43 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 1; New Profile: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 10:37:54 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 21:00:15 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 21:00:16 20216DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr 12 21:19:15 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 00:16:54 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 00:17:27 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 00:17:31 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 3; New Profile: 4.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 00:17:32 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 00:29:09 20215DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 00:34:05 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 02:18:22 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 2; New Profile: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 02:18:23 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 04:17:42 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 1; New Profile: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 04:17:52 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 20:45:36 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 20:49:19 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 20:57:51 20215DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 21:07:23 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 21:07:33 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 3; New Profile: 4.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 21:07:35 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 22:50:00 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 2; New Profile: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Apr 14 22:50:00 20216CM-STATUS message sent. Event Type Code: 21; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:16:10 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:16:25 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:17:11 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 4; New Profile: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:17:18 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:28:26 20215DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:30:11 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:31:34 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 3; New Profile: 4.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 00:31:52 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 02:17:35 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 2; New Profile: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 02:17:36 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 04:17:36 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 4; New Profile: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 04:25:25 20216CM-STATUS message sent. Event Type Code: 21; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 04:50:41 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: 3; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 04:50:42 20216CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 06:17:51 20216DS profile assignment change. DS Chan ID: 159; Previous Profile: ; New Profile: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Apr 15 06:18:04 20216CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
claum
  • 12
  • 0
  • 0
Joining in
201 Views
Message 8 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

0 Kudos
Reply
lotharmat
  • 937
  • 70
  • 142
Well-informed
187 Views
Message 9 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

Thanks for that!

I'm nit sure how to interpret the Up/downstream stats but the BQM points to a massive problem that VM will likely have to book an engineer to look at / fix.

They should pick this up pretty shortly!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

0 Kudos
Reply
claum
  • 12
  • 0
  • 0
Joining in
134 Views
Message 10 of 12
Flag for a moderator

Re: Gig1 Hub 4 packet loss

Does the upstream/downstream stuff look ok?
0 Kudos
Reply