cancel
Showing results for 
Search instead for 
Did you mean: 

Slow speed after upgrade to Gigabit

adhawkins
Up to speed

Hi all,

Upgraded to Gigabit yesterday. Barely getting 500 MBits/sec. Also, overnight our internet connection went down. It appeared that everything was connected (pfSense router reported it had an IP address, but no traffic being routed). Repowered the SuperHub, and it's back for now.

Superhub is in modem mode, with a pfsense router connected. All was previously fine when on 350M package, giving expected speeds up and down. Will post hub status in following messages.

18 REPLIES 18

adhawkins
Up to speed

3.0 Downstream channels

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

124990000006.50000040.366287QAM25612
14110000005.40000240.366287QAM2561
24190000005.59999838.605377QAM2562
34270000005.69999738.983261QAM2563
44350000006.00000038.605377QAM2564
54430000006.19999740.366287QAM2565
64510000006.59999840.366287QAM2566
74590000006.19999740.366287QAM2567
84670000006.19999740.366287QAM2568
94750000006.00000040.366287QAM2569
104830000006.19999740.366287QAM25610
114910000006.30000340.366287QAM25611
135070000006.40000240.366287QAM25613
145150000006.50000040.366287QAM25614
155230000006.59999840.366287QAM25615
165310000006.80000340.366287QAM25616
175390000007.00000040.366287QAM25617
185470000007.09999840.946209QAM25618
195550000007.09999840.366287QAM25619
205630000007.30000340.366287QAM25620
215710000007.40000240.366287QAM25621
225790000007.40000240.366287QAM25622
235870000007.40000240.946209QAM25623
245950000007.69999740.366287QAM25624
256030000007.90000240.366287QAM25625
266110000007.80000340.366287QAM25626
276190000007.80000340.366287QAM25627
286270000007.40000240.366287QAM25628
296350000007.30000340.366287QAM25629
306430000006.90000240.366287QAM25630
316510000007.00000040.946209QAM25631



3.0 Downstream channels

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

12Locked40.36628770
1Locked40.36628760
2Locked38.60537700
3Locked38.98326100
4Locked38.60537700
5Locked40.36628700
6Locked40.36628700
7Locked40.36628700
8Locked40.36628700
9Locked40.36628700
10Locked40.36628700
11Locked40.36628710
13Locked40.36628770
14Locked40.36628700
15Locked40.36628770
16Locked40.36628700
17Locked40.36628700
18Locked40.94620900
19Locked40.36628700
20Locked40.36628700
21Locked40.36628700
22Locked40.36628700
23Locked40.94620900
24Locked40.36628700
25Locked40.36628760
26Locked40.36628770
27Locked40.36628760
28Locked40.36628710
29Locked40.36628700
30Locked40.36628710
31Locked40.94620900



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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
41Locked425.1712720

3.0 Upstream channels

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

13260000042.5205995120 KSym/sec64QAM9
25370000042.7705995120 KSym/sec64QAM6
34620000042.5205995120 KSym/sec64QAM7
43940000042.5205995120 KSym/sec64QAM8



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

General Configuration

Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
cmreg-vmdg640-bbt076-b.cm



Primary Downstream Service Flow

SFID
61558
Max Traffic Rate
1230000450
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow

SFID
61557
Max Traffic Rate
55000270
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort

Network Log

Time Priority Description

Thu Jan 1 00:01:19 19704Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:52 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 7 14:41:21 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 7 14:44:27 20216SW Download INIT - Via Config file cmreg-vmdg640-bbt076-b.cm
Thu Oct 7 14:45:41 20216SW download Successful - Via Config file
Thu Oct 7 14:48:12 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 7 14:56:19 20215RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 7 14:56:25 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 41; 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 Oct 7 15:02:44 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 7 15:21:50 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:21 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 06:27:38 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 06:27:48 20215RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 06:28:03 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 41; 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;

12154033953

image.png

 

Very low error counts suggest the hub had been restarted shortly before the status data was taken.  It's usually best to post status data after a good few hours of run time (somewhere in the 12-48 hour range), because after a restart the hub erases all error counters, and the channels are freshly negotiated and may not be representative of the state they drift into if there's noise or power issues.  Having 1 Gbps is much more demanding of line quality than slower speeds, it's quite possible that any underlying issue existed before, but are only apparent now. 

I do observe that the power levels slope the wrong way (potentially an incorrectly setup amplifier in a street cabinet), but can't say whether the extent of that slope issue is great enough to cause speed problems.  DOCSIS is like most analogue technologies (for the most part) a pretty fault tolerant system, but at 1 Gbps any minor issues that don't affect lower speeds can crawl out of the woodwork.  

If you haven't already, could be worth undoing, wiping and remaking all coax joints with any nuts secured finger tight, checking cables for pinch or crush damage, and that all coax is VM supplied, and if there's a brown omnibox on the outside property wall, opening that and doing the same with the coax joints in that.  

Hi,

Yes, that data was posted about an hour after the hub was restarted to fix the problem that occurred overnight. I'll monitor the error counts, and post again later today.

Thanks for the advice regarding checking connections etc., will do that.

Andy

Ok, it's been running about 36 hours or so now. New results:

3.0 Downstream channels

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

124990000006.59999840.366287QAM25612
14110000005.40000240.366287QAM2561
24190000005.59999838.983261QAM2562
34270000005.80000338.983261QAM2563
44350000006.00000038.983261QAM2564
54430000006.19999740.366287QAM2565
64510000006.69999740.366287QAM2566
74590000006.30000340.366287QAM2567
84670000006.30000340.946209QAM2568
94750000006.09999840.366287QAM2569
104830000006.40000240.366287QAM25610
114910000006.40000240.366287QAM25611
135070000006.50000040.366287QAM25613
145150000006.59999840.366287QAM25614
155230000006.80000340.366287QAM25615
165310000006.90000240.366287QAM25616
175390000007.09999840.366287QAM25617
185470000007.09999840.366287QAM25618
195550000007.30000340.366287QAM25619
205630000007.50000040.946209QAM25620
215710000007.59999840.366287QAM25621
225790000007.80000340.366287QAM25622
235870000007.59999840.366287QAM25623
245950000007.80000340.366287QAM25624
256030000008.00000040.946209QAM25625
266110000007.80000340.946209QAM25626
276190000007.80000340.366287QAM25627
286270000007.40000240.366287QAM25628
296350000007.30000340.366287QAM25629
306430000007.00000040.366287QAM25630
316510000007.09999840.366287QAM25631



3.0 Downstream channels

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

12Locked40.36628700
1Locked40.36628700
2Locked38.98326100
3Locked38.98326100
4Locked38.98326100
5Locked40.36628700
6Locked40.36628700
7Locked40.36628700
8Locked40.94620900
9Locked40.36628710
10Locked40.36628700
11Locked40.36628700
13Locked40.36628700
14Locked40.36628720
15Locked40.36628700
16Locked40.36628700
17Locked40.36628700
18Locked40.36628700
19Locked40.36628710
20Locked40.94620900
21Locked40.36628700
22Locked40.36628710
23Locked40.36628700
24Locked40.36628710
25Locked40.94620920
26Locked40.94620910
27Locked40.36628720
28Locked40.36628720
29Locked40.36628710
30Locked40.36628720
31Locked40.36628710



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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
41Locked425.33289247110

3.0 Upstream channels

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

13260000042.7705995120 KSym/sec64QAM9
25370000043.2705995120 KSym/sec64QAM6
34620000042.7705995120 KSym/sec64QAM7
43940000042.7705995120 KSym/sec64QAM8



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000