cancel
Showing results for 
Search instead for 
Did you mean: 

HUB 4 to Zenwifi Pro XT12

BruceT
On our wavelength

Hi 

I want to connect a ASUS Zenwifi pro XT12 WiFi mesh system to my HUB 4 any recommendations best way to do this

any recommendations what mode to run the ASUS Router in

i take it I put HUB 4 in modem mode and connect wan port from ASUS to port 1 on HUB 4

any advice would be most appreciated please

wifi on HUB 4 very unstable so need the XT12 to boost signal and provide AX features for multiple devices and gamers in the house

thanks

15 REPLIES 15

Andrew-G
Alessandro Volta

any recommendations what mode to run the ASUS Router in

If you're running the hub in modem mode, then you have to run the Asus in router mode.  If you run the hub in router mode, Asus has to be in access point mode (I think Asus may use the term bridge mode, means the same thing).

Our general view is that there's no point running a VM hub in router mode with any competent mesh or third party router, because the hub's router will be inferior, although it will work if you need to run things that way.

jbrennand
Very Insightful Person
Very Insightful Person
And connect it in this sequence.....
____________________________

Switch on and set up your own router/Mesh unit (in its settings) with the WAN port set to be in Automatic IP i.e. DHCP (& Nat) mode, it may be pre-set that way anyway. Then, disconnect all cables from your new router (or Mesh first unit) and switch it off and unplug it. Then, put the VM Hub into modem mode
( https://www.virginmedia.com/help/virgin-media-hub-modem-mode )

and wait for the base light to turn magenta/purple (on a Hub3 - but not on a Hub4!). Once it’s in modem mode, the VM hub “MUST” then be powered off.

Then switch your router on and make sure it’s fully initialised (leave 5 min) and then put in the ethernet cable from its WAN port to the VM hub (any port will do).

NOW… power up the VM hub and wait 5-10 minutes for The Hub to initialise and and you should get a connection. Use the recommended App to connect any other Mesh units to the first one. This order only needs to be done the first time you connect the router to the VM hub.

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

BruceT
On our wavelength

Thanks gents setup went like a breeze and worked well and first time.

pity my hub 4 is still unstable and network needs to reconnect every now and then during the day. At least I now have world class ax based mesh network in my place and it’s is super quick when I have VM signal.

Andrew-G
Alessandro Volta

That's good.

Now let's see what we can do about the unreliable broadband:  Pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.  Then we can check for any obvious problems with power, noise or error counts.

BruceT
On our wavelength

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

253307500001.09999840.366287QAM25625
11387500001.29999938.605377QAM2561
21467500001.00000038.983261QAM2562
31547500001.20000138.983261QAM2563
41627500001.29999938.983261QAM2564
51707500001.09999840.366287QAM2565
61787500000.90000240.366287QAM2566
71867500000.90000240.366287QAM2567
81947500001.29999940.366287QAM2568
92027500001.09999840.366287QAM2569
102107500000.79999940.366287QAM25610
112187500001.09999840.366287QAM25611
122267500001.20000140.366287QAM25612
132347500001.40000240.946209QAM25613
142427500000.79999940.366287QAM25614
152507500000.70000140.366287QAM25615
162587500001.40000240.366287QAM25616
172667500001.40000240.366287QAM25617
182747500001.09999840.366287QAM25618
192827500001.20000140.366287QAM25619
202907500001.50000040.366287QAM25620
212987500001.40000240.366287QAM25621
223067500000.59999840.946209QAM25622
233147500000.40000240.366287QAM25623
243227500001.29999940.946209QAM25624
263387500000.70000140.366287QAM25626
273467500000.59999840.366287QAM25627
283547500001.00000040.366287QAM25628
293627500001.59999840.366287QAM25629
303707500001.20000140.366287QAM25630
313787500000.59999840.366287QAM25631



3.0 Downstream channels

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

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



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33944K1840QAM4096424


3.1 Downstream channels

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

BruceT
On our wavelength

Time Priority Description

Thu Mar 24 05:28:25 20223Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 24 05:28:25 20223Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 24 05:28:26 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 24 05:32:25 20223Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 24 05:32:41 20223Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 24 05:32:41 20223Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 24 05:33:25 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 24 05:33:50 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

BruceT
On our wavelength

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

15370000046.0205995120 KSym/sec64QAM2
23940000045.5205995120 KSym/sec64QAM4
34620000045.7705995120 KSym/sec64QAM3
46030000046.7705995120 KSym/sec64QAM1



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

BruceT
On our wavelength

@Andrew_G the upstream has no errors now as this was a post-reboot of Hub I had to do this AM. I took photos of the logs and  status, what I saw was T3 timeout of Chan 1 =-31 2=284 3=285 4 = 309 all channels 64QAM modulation

The  Hub is having to reset the connection due to up and downstream errors upwards of every 30 to 60 mins during the day. VM Technical have replaced the hub beginning of the week thinking it may be the hub after a line test was very successful but I'm starting to think it is not the hub. I have a new line pulled into the cabinet in late Jan so the last mile is brand new and the installation was brand new.  

For some reason, I do get some stability in the afternoon  but then at around 7 pm the Hub starts to reset the broadband connection, when I look at the stats the errors happening on T3 timeouts is  fairly big as per above in some cases  as well as downstream pre and post rs errors

The HUb is running in Modem mode

BruceT
On our wavelength
At the moment im connected