Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Received Hub4

lojelo5
Superfast

on ‎05-12-2021 02:51

Just received the hub4 from volt upgrade, I didn't want to do this because I wasn't really bothered about the 1gb package but a nice lady at VM offered us a better package at a nice price, I had to take it because the wife said so!!

I have no problems with the download/upload I'm getting the full speed you can get from this hub12423252273

I just want to know why the Modulation (Active Profile) keeps reverting back to QAM1024 when it should be QAM4096. I have tried rebooting a few times, done a pinhole reset several times but each time I get it back to QAM4096 few minutes later it goes back to QAM1024.

 

 

Cable Modem Status
Item	Status	Comments
Cable Modem Status	
Online
DOCSIS 3.1
Primary downstream channel	
Locked
SC-QAM
Channel Overview	Downstream	Upstream
DOCSIS 3.0 channels	
31
4
DOCSIS 3.1 channels	
1
0
3.0 Downstream channels
Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
25	331000000	1.900002	38.605377	QAM256	25
32	387000000	0.500000	38.605377	QAM256	32
33	491000000	0.599998	38.983261	QAM256	33
34	499000000	0.799999	38.605377	QAM256	34
4	163000000	3.299999	38.605377	QAM256	4
5	171000000	3.200001	38.983261	QAM256	5
6	179000000	3.099998	38.983261	QAM256	6
7	187000000	3.099998	38.605377	QAM256	7
8	195000000	2.900002	38.983261	QAM256	8
9	203000000	2.700001	38.605377	QAM256	9
10	211000000	2.500000	38.983261	QAM256	10
11	219000000	2.500000	38.605377	QAM256	11
12	227000000	2.200001	38.605377	QAM256	12
13	235000000	2.000000	38.605377	QAM256	13
14	243000000	1.700001	38.605377	QAM256	14
15	251000000	1.500000	38.605377	QAM256	15
16	259000000	1.599998	38.983261	QAM256	16
17	267000000	2.000000	38.605377	QAM256	17
18	275000000	2.099998	38.983261	QAM256	18
19	283000000	2.099998	38.605377	QAM256	19
20	291000000	2.000000	38.983261	QAM256	20
21	299000000	2.000000	38.983261	QAM256	21
22	307000000	2.000000	38.983261	QAM256	22
23	315000000	2.000000	38.983261	QAM256	23
24	323000000	1.799999	38.605377	QAM256	24
26	339000000	1.799999	38.605377	QAM256	26
27	347000000	1.900002	38.605377	QAM256	27
28	355000000	2.099998	38.605377	QAM256	28
29	363000000	1.599998	38.983261	QAM256	29
30	371000000	1.200001	38.605377	QAM256	30
31	379000000	0.799999	38.605377	QAM256	31


3.0 Downstream channels
Channel	Lock Status	RxMER (dB)	Pre RS Errors	Post RS Errors
25	Locked	38.605377	0	0
32	Locked	38.605377	0	0
33	Locked	38.983261	0	0
34	Locked	38.605377	0	0
4	Locked	38.605377	0	0
5	Locked	38.983261	0	0
6	Locked	38.983261	0	0
7	Locked	38.605377	0	0
8	Locked	38.983261	0	0
9	Locked	38.605377	0	0
10	Locked	38.983261	0	0
11	Locked	38.605377	0	0
12	Locked	38.605377	0	0
13	Locked	38.605377	0	0
14	Locked	38.605377	0	0
15	Locked	38.605377	0	0
16	Locked	38.983261	0	0
17	Locked	38.605377	0	0
18	Locked	38.983261	0	0
19	Locked	38.605377	0	0
20	Locked	38.983261	0	0
21	Locked	38.983261	0	0
22	Locked	38.983261	0	0
23	Locked	38.983261	0	0
24	Locked	38.605377	0	0
26	Locked	38.605377	0	0
27	Locked	38.605377	0	0
28	Locked	38.605377	0	0
29	Locked	38.983261	0	0
30	Locked	38.605377	0	0
31	Locked	38.605377	0	0


3.1 Downstream channels
Channel	Channel Width (MHz)	FFT Type	Number of Active Subcarriers	Modulation (Active Profile)	First Active Subcarrier (Hz)
159	96	4K	1880	QAM1024	392


3.1 Downstream channels
Channel ID	Lock Status	RxMER Data (dB)	PLC Power (dBmV)	Correcteds (Active Profile)	Uncorrectables (Active Profile)
159	Locked	41	1.2	4551330	0
3.0 Upstream channels
Channel	Frequency (Hz)	Power (dBmV)	Symbol Rate (ksps)	Modulation	Channel ID
1	53700000	48.520599	5120 KSym/sec	64QAM	2
2	39400000	47.770599	5120 KSym/sec	64QAM	4
3	46200000	48.270599	5120 KSym/sec	64QAM	3
4	60300000	49.270599	5120 KSym/sec	64QAM	1


3.0 Upstream channels
Channel	Channel Type	T1 Timeouts	T2 Timeouts	T3 Timeouts	T4 Timeouts
1	US_TYPE_STDMA	0	0	1	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

 

 

 

 

 

General Configuration
Network access	
true
Maximum Number of CPEs	
1
Baseline Privacy	
true
DOCSIS Mode	
3.1
Config file	
cxv9873254k;fg87dsfd;kfoA


Primary Downstream Service Flow
SFID	
3904
Max Traffic Rate	
1200000450
Max Traffic Burst	
42600
Min Traffic Rate	
0


Primary Upstream Service Flow
SFID	
3903
Max Traffic Rate	
55000270
Max Traffic Burst	
42600
Min Traffic Rate	
0
Max Concatenated Burst	
16320
Scheduling Type	
bestEffort

 

 

 

 

 

Network Log
Time	Priority	Description
Thu Jan 1 00:01:24 1970	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 00:14:57 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 00:27:13 2021	5	DBC-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 Jan 1 00:01:19 1970	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 01:12:27 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 01:24:42 2021	5	DBC-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;

 

 

 

I have also run a test on my connection via the service page this has come back several times telling me I have a broadband issue? saying it will send a signal to my hub in order to fix things but does nothing at all.

I have also setup a new BQM not much showing on this I only set it up yesterday but it does look pretty bad.

81b576f260c9ff0f0e8fdf94668231b750e38ed2-04-12-2021

961f4a09820c8563760e76fbe31f29d2ceeee355-05-12-2021

0 Kudos
9 REPLIES 9

Adduxi
Very Insightful Person
Very Insightful Person

on ‎05-12-2021 12:30

It should be 4096, but has dropped to 1024 to cope with, at a guess, noise on the circuit.  Also your BQM is showing evidence of packet loss. 

Either phone VM or wait here a day or two for a VM Mod to pick this up.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos

lojelo5
Superfast
In response to Adduxi

on ‎05-12-2021 12:42

The issues seen it that graph could have also been caused by myself I unattached the isolater cable a couple of times when the hub was still powered up, will put another graph up in a day or so see if it settles.

0 Kudos

lojelo5
Superfast
In response to lojelo5

on ‎06-12-2021 00:50

This is an up to date graph

1df4e115f93149a1ea4e14f408f14f0dffdeef8a-06-12-2021

Downstream is now on QAM2048

3.1 Downstream channels
Channel	Channel Width (MHz)	FFT Type	Number of Active Subcarriers	Modulation (Active Profile)	First Active Subcarrier (Hz)
159	96	4K	1880	QAM2048	392


3.1 Downstream channels
Channel ID	Lock Status	RxMER Data (dB)	PLC Power (dBmV)	Correcteds (Active Profile)	Uncorrectables (Active Profile)
159	Locked	41	1.2	71396706	0
0 Kudos

Paul_DN
Forum Team
Forum Team
In response to lojelo5

on ‎08-12-2021 09:20

Hi lojelo5,

Thank you for reaching out to us in our community and welcome back, your most recent BQM looks a lot better, I have had a look our end and cannot see any issues at all, how are things today?

Regards

Paul.

 

0 Kudos

lojelo5
Superfast
In response to Paul_DN

on ‎08-12-2021 22:20

Thanks for getting back Paul

Apart from the QAM still being 1024, should be 4096 things don't look too bad.

 

Today's BQM

24870733455c6e8f0e5bf2fea67d0e5f2b19e27b-08-12-2021

Has you can see QAM still on 1024, no matter doing a pinhole reset it just keeps reverting back to 1024.

3.1 Downstream channels
Channel	Channel Width (MHz)	FFT Type	Number of Active Subcarriers	Modulation (Active Profile)	First Active Subcarrier (Hz)
159	96	4K	1880	QAM1024	392


3.1 Downstream channels
Channel ID	Lock Status	RxMER Data (dB)	PLC Power (dBmV)	Correcteds (Active Profile)	Uncorrectables (Active Profile)
159	Locked	43	1.5	52831330	0

 

0 Kudos

Zoie_P
Forum Team (Retired)
Forum Team (Retired)
In response to lojelo5

on ‎11-12-2021 10:16

Hi lojelo5, 

Thanks for your reply, I have checked your power levels and your hub etc on our side and all looks okay. 

Please keep us posted.

Zoie

0 Kudos

lojelo5
Superfast
In response to Zoie_P

‎11-12-2021 21:10 - edited ‎11-12-2021 21:11

I only just noticed this in my hubs networklog is this just a bug, the dates! 1st time I've seen any Pre RS errors show as well.

 

Thu Jan 1 00:01:24 1970

 

 

Network Log
Time	Priority	Description
Thu Jan 1 00:01:24 1970	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 00:14:57 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 00:27:13 2021	5	DBC-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 Jan 1 00:01:19 1970	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 01:12:27 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 5 01:24:42 2021	5	DBC-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 Dec 6 16:17:01 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 6 16:29:16 2021	5	DBC-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;
Tue Dec 7 06:04:08 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Dec 7 06:16:23 2021	5	DBC-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 Dec 9 11:42:45 2021	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 9 11:42:46 2021	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Dec 11 20:46:30 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Dec 11 20:58:46 2021	5	DBC-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;

 

 

  

 

3.0 Downstream channels
Channel	Frequency (Hz)	Power (dBmV)	SNR (dB)	Modulation	Channel ID
25	331000000	2.000000	38.983261	QAM256	25
32	387000000	0.700001	40.366287	QAM256	32
33	491000000	0.700001	40.946209	QAM256	33
34	499000000	0.799999	40.366287	QAM256	34
4	163000000	3.799999	40.366287	QAM256	4
5	171000000	3.599998	40.366287	QAM256	5
6	179000000	3.500000	40.366287	QAM256	6
7	187000000	3.400002	40.366287	QAM256	7
8	195000000	3.299999	40.366287	QAM256	8
9	203000000	3.000000	40.366287	QAM256	9
10	211000000	2.900002	40.366287	QAM256	10
11	219000000	2.700001	40.366287	QAM256	11
12	227000000	2.400002	40.946209	QAM256	12
13	235000000	2.200001	40.366287	QAM256	13
14	243000000	2.000000	40.366287	QAM256	14
15	251000000	1.700001	40.366287	QAM256	15
16	259000000	2.000000	40.366287	QAM256	16
17	267000000	2.299999	40.946209	QAM256	17
18	275000000	2.400002	40.366287	QAM256	18
19	283000000	2.400002	40.366287	QAM256	19
20	291000000	2.299999	40.366287	QAM256	20
21	299000000	2.200001	40.366287	QAM256	21
22	307000000	2.200001	40.946209	QAM256	22
23	315000000	2.200001	40.366287	QAM256	23
24	323000000	2.000000	40.366287	QAM256	24
26	339000000	1.900002	40.366287	QAM256	26
27	347000000	2.200001	40.946209	QAM256	27
28	355000000	2.200001	40.366287	QAM256	28
29	363000000	1.799999	40.366287	QAM256	29
30	371000000	1.200001	38.983261	QAM256	30
31	379000000	0.700001	38.983261	QAM256	31


3.0 Downstream channels
Channel	Lock Status	RxMER (dB)	Pre RS Errors	Post RS Errors
25	Locked	38.983261	0	0
32	Locked	40.366287	2	0
33	Locked	40.946209	0	0
34	Locked	40.366287	4	0
4	Locked	40.366287	0	0
5	Locked	40.366287	0	0
6	Locked	40.366287	0	0
7	Locked	40.366287	0	0
8	Locked	40.366287	0	0
9	Locked	40.366287	0	0
10	Locked	40.366287	8	0
11	Locked	40.366287	7	0
12	Locked	40.946209	0	0
13	Locked	40.366287	9	0
14	Locked	40.366287	7	0
15	Locked	40.366287	0	0
16	Locked	40.366287	0	0
17	Locked	40.946209	7	0
18	Locked	40.366287	0	0
19	Locked	40.366287	0	0
20	Locked	40.366287	0	0
21	Locked	40.366287	0	0
22	Locked	40.946209	7	0
23	Locked	40.366287	7	0
24	Locked	40.366287	0	0
26	Locked	40.366287	0	0
27	Locked	40.946209	7	0
28	Locked	40.366287	6	0
29	Locked	40.366287	0	0
30	Locked	38.983261	3	0
31	Locked	38.983261	3	0

 

 

Still no problem with speed.

0 Kudos

Tudor
Very Insightful Person
Very Insightful Person
In response to lojelo5

on ‎11-12-2021 22:17

You get Jan 1 1970 a lot in the hubs log, it’s not an error. When the hub starts/restarts it does not have the date/time so a default one is used. Once the date/time has been obtained from the VM CMTS the hubs date/time is set correctly. 


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos

lojelo5
Superfast
In response to Tudor

on ‎11-12-2021 22:34

It must be rebooting itself quite a lot then, I've had more default dates showing than I have rebooted it, it's not causing any issues I have noticed so it's fine with me for now.

0 Kudos
Top