13-01-2022 19:42 - edited 13-01-2022 19:45
Hi
I have just upgraded (10/01/22) to the 1 gig and I have managed to get the Sam knows speed test to work and it doesn't seem like I'm getting the speed to the hub.
I'm basically getting the same as before the upgrade.
Answered! Go to Answer
on 13-01-2022 20:49
@spacecadetuk wrote:thanks again for looking at this for meGeneral Configuration
Network access trueMaximum Number of CPEs 1Baseline Privacy trueDOCSIS Mode 3.1Config file 54k;fg87dsfd;kfoA,.iyewrkPrimary Downstream Service Flow
SFID 32640Max Traffic Rate 690000278Max Traffic Burst 42600Min Traffic Rate 0Primary Upstream Service Flow
SFID 32639Max Traffic Rate 44000278Max Traffic Burst 42600Min Traffic Rate 0Max Concatenated Burst 42600Scheduling Type bestEffort
Well there is your answer! You are still configured for 600 Mbps!
Try a full reset on the HUB (30 second press of the reset button).
Keep in mind all settings revert to default.
on 13-01-2022 19:42
26 | 338750000 | 6.400002 | 40.946209 | QAM256 | 26 |
1 | 138750000 | 8.099998 | 40.946209 | QAM256 | 1 |
2 | 146750000 | 8.199997 | 40.946209 | QAM256 | 2 |
3 | 154750000 | 8.099998 | 40.946209 | QAM256 | 3 |
4 | 162750000 | 6.500000 | 40.366287 | QAM256 | 4 |
5 | 170750000 | 7.599998 | 40.946209 | QAM256 | 5 |
6 | 178750000 | 8.400002 | 40.946209 | QAM256 | 6 |
7 | 186750000 | 8.199997 | 40.946209 | QAM256 | 7 |
8 | 194750000 | 7.900002 | 40.946209 | QAM256 | 8 |
9 | 202750000 | 8.099998 | 40.946209 | QAM256 | 9 |
10 | 210750000 | 7.900002 | 40.366287 | QAM256 | 10 |
11 | 218750000 | 7.800003 | 40.946209 | QAM256 | 11 |
12 | 226750000 | 7.699997 | 40.366287 | QAM256 | 12 |
13 | 234750000 | 7.599998 | 40.366287 | QAM256 | 13 |
14 | 242750000 | 7.900002 | 40.366287 | QAM256 | 14 |
15 | 250750000 | 7.800003 | 40.946209 | QAM256 | 15 |
16 | 258750000 | 8.099998 | 40.366287 | QAM256 | 16 |
17 | 266750000 | 7.599998 | 40.946209 | QAM256 | 17 |
18 | 274750000 | 7.000000 | 40.946209 | QAM256 | 18 |
19 | 282750000 | 7.000000 | 40.366287 | QAM256 | 19 |
20 | 290750000 | 7.099998 | 40.366287 | QAM256 | 20 |
21 | 298750000 | 7.800003 | 40.366287 | QAM256 | 21 |
22 | 306750000 | 7.300003 | 40.366287 | QAM256 | 22 |
23 | 314750000 | 6.900002 | 40.366287 | QAM256 | 23 |
24 | 322750000 | 6.000000 | 40.366287 | QAM256 | 24 |
25 | 330750000 | 6.500000 | 40.366287 | QAM256 | 25 |
27 | 346750000 | 6.500000 | 40.366287 | QAM256 | 27 |
28 | 354750000 | 6.800003 | 40.946209 | QAM256 | 28 |
29 | 362750000 | 6.800003 | 40.946209 | QAM256 | 29 |
30 | 370750000 | 6.800003 | 40.366287 | QAM256 | 30 |
31 | 378750000 | 7.000000 | 40.946209 | QAM256 | 31 |
26 | Locked | 40.946209 | 3 | 0 |
1 | Locked | 40.946209 | 0 | 0 |
2 | Locked | 40.946209 | 0 | 0 |
3 | Locked | 40.946209 | 0 | 0 |
4 | Locked | 40.366287 | 0 | 0 |
5 | Locked | 40.946209 | 9 | 0 |
6 | Locked | 40.946209 | 0 | 0 |
7 | Locked | 40.946209 | 64 | 0 |
8 | Locked | 40.946209 | 1 | 0 |
9 | Locked | 40.946209 | 0 | 0 |
10 | Locked | 40.366287 | 0 | 0 |
11 | Locked | 40.946209 | 1 | 0 |
12 | Locked | 40.366287 | 1 | 0 |
13 | Locked | 40.366287 | 1 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.946209 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.946209 | 0 | 0 |
18 | Locked | 40.946209 | 0 | 0 |
19 | Locked | 40.366287 | 0 | 0 |
20 | Locked | 40.366287 | 1 | 0 |
21 | Locked | 40.366287 | 1 | 0 |
22 | Locked | 40.366287 | 2 | 0 |
23 | Locked | 40.366287 | 2 | 0 |
24 | Locked | 40.366287 | 1 | 0 |
25 | Locked | 40.366287 | 1 | 0 |
27 | Locked | 40.366287 | 6 | 0 |
28 | Locked | 40.946209 | 8 | 0 |
29 | Locked | 40.946209 | 6 | 0 |
30 | Locked | 40.366287 | 3 | 0 |
31 | Locked | 40.946209 | 3 | 0 |
159 | 94 | 4K | 1840 | QAM4096 | 424 |
159 | Locked | 43 | 6.1 | 410121286 | 0 |
on 13-01-2022 19:43
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 |
13-01-2022 20:11 - edited 13-01-2022 20:15
Very odd as the stats and BQM look pretty good! Power levels on downstream a touch high but in spec. Anything in the Networklog tab? Oh could you post the upstream tab data also?
The only difference I've noted, when compared to mine, is the 'Channel Width', 'Number of Active Subcarriers', and First Active Subcarrier' are different values:
Mine:
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 | 96 | 4K | 1880 | QAM4096 | 759 |
Yours:
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159 | 94 | 4K | 1840 | QAM4096 | 424 |
A bit over my head if this would make a massive difference to your connection!
on 13-01-2022 20:26
thanks for the reply, I'm not sure if its been upgraded to be honest.
here is the network log
TimePriorityDescriptionThu Jan 1 00:01:17 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 18:33:51 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 18:33:51 20223Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 18:33:51 20224T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 18:33:52 20223REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 18:34:20 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 18:34:45 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 18:34:58 20226SW Download INIT - Via Config file a69834ncxv9873254k;fg87dsTue Jan 11 18:36:11 20226SW download Successful - Via Config fileTue Jan 11 18:38:43 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 19:06:04 20224DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 19:06:05 20226DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 20:04:52 20224DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 20:04:52 20226DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Jan 11 21:47:24 20226CM-STATUS message sent. Event Type Code: 24; 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 Jan 12 12:44:43 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed Jan 12 19:18:06 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
upstream stats
1 | 46200000 | 43.020599 | 5120 KSym/sec | 64QAM | 1 |
2 | 25800000 | 42.270599 | 5120 KSym/sec | 64QAM | 4 |
3 | 32600000 | 42.270599 | 5120 KSym/sec | 64QAM | 3 |
4 | 39400000 | 42.270599 | 5120 KSym/sec | 64QAM | 2 |
1 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
on 13-01-2022 20:30
on 13-01-2022 20:39
That's a good point (Upstream looks healthy btw)!
What does your configuration tab look like?
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | 87dsfd;kfoA,.iyewrkldJKDH |
SFID | 889 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 1420 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | bestEffort |
13-01-2022 20:47 - edited 13-01-2022 20:49
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | 54k;fg87dsfd;kfoA,.iyewrk |
SFID | 32640 |
Max Traffic Rate | 690000278 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 32639 |
Max Traffic Rate | 44000278 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
I don't know anything about these stats but the max traffic rate looks the culprit to me?
on 13-01-2022 20:49
@spacecadetuk wrote:thanks again for looking at this for meGeneral Configuration
Network access trueMaximum Number of CPEs 1Baseline Privacy trueDOCSIS Mode 3.1Config file 54k;fg87dsfd;kfoA,.iyewrkPrimary Downstream Service Flow
SFID 32640Max Traffic Rate 690000278Max Traffic Burst 42600Min Traffic Rate 0Primary Upstream Service Flow
SFID 32639Max Traffic Rate 44000278Max Traffic Burst 42600Min Traffic Rate 0Max Concatenated Burst 42600Scheduling Type bestEffort
Well there is your answer! You are still configured for 600 Mbps!
Try a full reset on the HUB (30 second press of the reset button).
Keep in mind all settings revert to default.
on 13-01-2022 20:53