Hub4 in modem mode

[mattwellsy]

Hello

Been having issues with my internet thought it was a fault in the area.  It would seem for some reason my hub4 in modem mode is still using 192.168.0.1 IP, causing my edgerouter 4 to have a Ip conflict and it drops the VM connection to use my backup.  No idea why its doing it been working for months with no issues, spent 6 hours trying to work out why factory resetting Hub4 and Edgerouter 4 with no joy.

To get me up and running using the router not in modem mode to the edge router which I changed its IP, would be ok if I did not have a Pihole system, printers, nas all on the 192.168.0.1 network.

Anyone ran in to the hub4 in modem mode still using 192.168.0.1 and been unable to fix?

Thanks

[mattwellsy]

I have the Hub4 in modem mode, edgerouter 4 has a 82.29.*.* connection via it but still no internet with VM, if I unplug my backup no internet so I know the internet is not working via the VM network.  Works when directly connected to PC in router mode and modem mode but no idea why not when connected to the edgerouter 4

[Tudor]

See instructions and notes below:

How to put a VM hub into modem mode:

1) Access your hub on 192.168.0.1, sign on and put it into modem mode. On the Hub3 the bottom LED will change to magenta, on a Hub4 the LED band will be green. Best done from a wired connection.

2) Turn off the hub and disconnect any Ethernet cables

3) Fully initialise your own router or mesh master unit and make sure the WAN port is set to DHCP (for some routers or mesh this may have to be done in router mode before entering modem mode)

4) Connect your router or mesh master unit to the VM hub with an Ethernet cable, Cat5e or Cat6, any higher specification is a waste of money

5) Turn on the VM hub. 

6) You should now be able to access the internet and the hub will now be on 192.168.100.1

Note1: this only needs doing once for each new router or VM changes your WAN IP address.

Note2: If you have a Hub4 and your own router is NOT 192.168.0.1 then it’s possible that you can still access the VM hub on 192.168.0.1

[Adri_G]

Hey mattwesley, thanks for posting on our help forum with this issue.

We're sorry to hear your hub 4 is not working well with the 3rd party equipment connected to it, as you advised your hub 4 is on modem mode this could be a problem with the edgerouter instead.
This sounds like an IP related issue with your non-VM equipment, have you checked this with the manufacturer to see what they advise on their end?

Also, has the advice from Tudor above helped with the issue at all and have you seen any improvements since you last posted here on Tuesday?
Let us know of these and we're happy to assist further.

[legacy1]

The hub using 192.168.0.1 will not cause a problem because Edgerouter has 192.168.0.1 and has no reason to send out the WAN the only time its a problem is if the WAN get an IP 192.168.0.0/24 which is not the case here.

[mattwellsy]

Hello

Thanks for the information, but still cannot get it working as it was.

Hub mode connected to edgerouter works

Modem Mode does not seems to get it address but if I go to that ip address its my edge router

thought it might be a MAC address issue as modem mode connected direct to PC works without any issue. So I cloned mac from PC ethernet adaptor to edge router eth0 connection still no joy.

Not sure what the issue is when in modem mode using edge router also cannot see hub on 192.168.100.1, can when connected direct to PC. If I mode backup connected to eth0 on  edge router it works so I know the port is ok and works.  I don't have anything other than default setting a load balancing setup, with only use eth1 if eth0 is down, which is what it is doing.

So Hub seems to go into Modem mode fine, get internet when connected direct to PC, but not via the edge router 4.

I have tested ethernet cables, no issues on the 4 pairs cable is fine, I have also changed cable just in case.

It seems that the edge router is not getting the correct info back from the hub in modem mode to allow it to connect.

Will take a look at the logs but have to disconnect to will post this first

[mattwellsy]

Hub log in modem mode, As internet is important within the house hold I can only mess with it at odd hours.

Network Log

Time Priority Description

Thu Jan 1 00:01:28 1970	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 27 09:58:20 2022	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 Sep 27 10:09:36 2022	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 Sep 27 15:27:15 2022	6	CM-STATUS message sent. Event Type Code: 24; 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 Sep 28 18:30:12 2022	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 30 05:49:28 2022	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 30 06:00:43 2022	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;
Fri Sep 30 06:13:55 2022	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 30 06:21:59 2022	6	CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 395052; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 30 06:39:26 2022	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Sep 30 06:50:44 2022	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 Upstream channels

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

1	25800000	49.270599	5120 KSym/sec	32QAM	14
2	32600000	48.770599	5120 KSym/sec	64QAM	13
3	39400000	48.270599	5120 KSym/sec	64QAM	12
4	46200000	48.270599	5120 KSym/sec	64QAM	11

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

3.0 Downstream channels

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

25	330750000	-0.700001	38.605377	QAM256	25
10	210750000	1.400002	40.366287	QAM256	10
11	218750000	1.200001	40.366287	QAM256	11
12	226750000	0.700001	38.983261	QAM256	12
13	234750000	0.400002	38.983261	QAM256	13
14	242750000	0.200001	40.366287	QAM256	14
15	250750000	-0.099998	38.983261	QAM256	15
16	258750000	0.000000	38.983261	QAM256	16
17	266750000	0.200001	38.983261	QAM256	17
18	274750000	0.200001	38.983261	QAM256	18
19	282750000	-0.400002	38.983261	QAM256	19
20	290750000	-0.599998	38.983261	QAM256	20
21	298750000	-0.500000	38.983261	QAM256	21
22	306750000	-0.099998	40.366287	QAM256	22
23	314750000	-0.099998	38.605377	QAM256	23
24	322750000	-0.200001	38.983261	QAM256	24
26	338750000	-0.500000	38.983261	QAM256	26
27	346750000	-0.700001	40.366287	QAM256	27
28	354750000	-0.900002	38.605377	QAM256	28
29	362750000	-0.900002	38.605377	QAM256	29
30	370750000	-1.099998	38.983261	QAM256	30
31	378750000	-1.099998	38.983261	QAM256	31
9	202750000	1.599998	40.366287	QAM256	9
1	138750000	2.000000	38.983261	QAM256	1
2	146750000	1.700001	38.983261	QAM256	2
3	154750000	1.799999	40.366287	QAM256	3
4	162750000	1.799999	40.946209	QAM256	4
5	170750000	1.799999	40.366287	QAM256	5
6	178750000	1.799999	40.366287	QAM256	6
7	186750000	1.799999	40.946209	QAM256	7
8	194750000	1.599998	40.366287	QAM256	8

[mattwellsy]

3.0 Downstream channels

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

25	Locked	38.605377	0	0
10	Locked	40.366287	0	0
11	Locked	40.366287	6	0
12	Locked	38.983261	0	0
13	Locked	38.983261	8	0
14	Locked	40.366287	0	0
15	Locked	38.983261	0	0
16	Locked	38.983261	0	0
17	Locked	38.983261	0	0
18	Locked	38.983261	0	0
19	Locked	38.983261	2	0
20	Locked	38.983261	4	0
21	Locked	38.983261	3	0
22	Locked	40.366287	11	0
23	Locked	38.605377	3	0
24	Locked	38.983261	6	0
26	Locked	38.983261	7	0
27	Locked	40.366287	0	0
28	Locked	38.605377	1	0
29	Locked	38.605377	1	0
30	Locked	38.983261	0	0
31	Locked	38.983261	1	0
9	Locked	40.366287	0	0
1	Locked	38.983261	0	0
2	Locked	38.983261	0	0
3	Locked	40.366287	0	0
4	Locked	40.946209	0	0
5	Locked	40.366287	0	0
6	Locked	40.366287	0	0
7	Locked	40.946209	0	0
8	Locked	40.366287	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

QAM4096

759

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159

Locked

42

-2.5

3449065

0

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

Connected via Hub in modem mode via PC no problem, So cannot work out why the edge router 4 does not work. I have noticed it does get a different IP when connected via PC and the via edgerouter could it be a validation issue?

Thanks

[mattwellsy]

Did a service check today, had nothing last few days, but today

Looks like there’s still an issue with your connection

We’re looking into it. Check back here after 23 hours and if there’s still an issue we’ll help you book a technician.

So maybe that's the issue? still does no explain it seeming to work without error if directly connected to PC, and in hub mode when connected to Edgerouter

[Tudor]

The critical part of the instructions is that once the hub is in modem mode it must be turned off. It must be the last bit of equipment turned on.