Menu
Reply
Icantcrabhere
  • 118
  • 1
  • 13
Dialled in
529 Views
Message 1 of 4
Flag for a moderator

Slight overutilisation/noisy TBB

Hi again!
Although my previous major packetloss issues were fixed, (few little dots here and there, but nothing out of the normal)
I really want to solve the next issue.

I know we're currently again in lockdown, but even before this my TBB graphs have always been pretty "Spikey" "Noisy".
Even without the elevated levels of traffic/usage in lockdown (Which are pretty much being nearly pushed to the limit in my area, I'd assume)

LIVE GRAPH:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/3f9a0c6eff35d57ae0f42e221bb1b8b92039be2d

Based in Hemel Hempstead, not sure on the area code.
speeds are as expected, 100~108MB download, 9~10MB up.
Wired connection, modem mode, Superhub 3.

Following posts with hub3 stats, just for good measure 🙂

I should note, 10 of those T3 timeouts that you see in my upcoming stat posts, happened in one burst.
The others were spread out.

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
531000000
Locked
Ranged Upstream Channel (Hz)
25800078
Locked
Provisioning State
Online
 

 

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

15310000003.740256 qam16
24110000006.540256 qam1
3419000000640256 qam2
4427000000640256 qam3
54350000005.940256 qam4
64430000005.940256 qam5
74510000005.840256 qam6
84590000005.540256 qam7
94670000005.140256 qam8
10475000000540256 qam9
11483000000540256 qam10
124910000005.340256 qam11
134990000005.140256 qam12
14507000000540256 qam13
155150000004.440256 qam14
165230000003.940256 qam15
17539000000440256 qam17
185470000004.340256 qam18
195550000004.540256 qam19
20563000000440256 qam20
215710000003.240256 qam21
225790000002.540256 qam22
235870000002.740256 qam23
245950000003.440256 qam24



Downstream bonded channels

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

1Locked40.32250
2Locked40.9810
3Locked40.93710
4Locked40.3740
5Locked40.91810
6Locked40.91380
7Locked40.9670
8Locked40.92490
9Locked40.9780
10Locked40.9360
11Locked40.91150
12Locked40.9890
13Locked40.9950
14Locked40.31170
15Locked40.9570
16Locked40.33930
17Locked40.3810
18Locked40.32700
19Locked40.9710
20Locked40.95890
21Locked40.32230
22Locked40.32100
23Locked40.34540
24Locked40.31560



0 Kudos
Reply
Icantcrabhere
  • 118
  • 1
  • 13
Dialled in
528 Views
Message 2 of 4
Flag for a moderator

Re: Slight overutilisation/noisy TBB

Upstream bonded channels

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

12580007840.5512064 qam4
24620015442512064 qam1
33940000041.5512064 qam2
43260000041512064 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0000
3ATDMA00120
4ATDMA0000

 

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-bbt057-b.cm



Primary Downstream Service Flow

SFID496838
Max Traffic Rate117000047
Max Traffic Burst42600
Min Traffic Rate0
0 Kudos
Reply
Icantcrabhere
  • 118
  • 1
  • 13
Dialled in
527 Views
Message 3 of 4
Flag for a moderator

Re: Slight overutilisation/noisy TBB

etwork Log

Time Priority Description

04/01/2021 09:02:51ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/01/2021 16:29:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2020 21:02:50ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2020 14:05:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/12/2020 19:48:31ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/12/2020 06:12:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2020 07:48:31ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/12/2020 19:30:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/12/2020 19:48:30ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/12/2020 03:23:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/12/2020 15:54:23ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 16:12:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/12/2020 10:42:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/12/2020 03:40:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/12/2020 22:42:43ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/12/2020 17:43:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/12/2020 10:42:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/11/2020 04:31:3criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/11/2020 22:42:41ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/11/2020 20:47:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Icantcrabhere
  • 118
  • 1
  • 13
Dialled in
505 Views
Message 4 of 4
Flag for a moderator

Re: Slight overutilisation/noisy TBB

Also should note,
I still sometimes see my upstream modulation dropping,
This was one of the more recent ones I observed,
(Picture will need to be approved)

noise 27th.png

0 Kudos
Reply