on 22-03-2022 14:34
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
on 22-03-2022 14:42
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.
on 22-03-2022 15:03
on 23-03-2022 20:54
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.
on 24-03-2022 07:23
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.
on 24-03-2022 09:20
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | 1.099998 | 40.366287 | QAM256 | 25 |
1 | 138750000 | 1.299999 | 38.605377 | QAM256 | 1 |
2 | 146750000 | 1.000000 | 38.983261 | QAM256 | 2 |
3 | 154750000 | 1.200001 | 38.983261 | QAM256 | 3 |
4 | 162750000 | 1.299999 | 38.983261 | QAM256 | 4 |
5 | 170750000 | 1.099998 | 40.366287 | QAM256 | 5 |
6 | 178750000 | 0.900002 | 40.366287 | QAM256 | 6 |
7 | 186750000 | 0.900002 | 40.366287 | QAM256 | 7 |
8 | 194750000 | 1.299999 | 40.366287 | QAM256 | 8 |
9 | 202750000 | 1.099998 | 40.366287 | QAM256 | 9 |
10 | 210750000 | 0.799999 | 40.366287 | QAM256 | 10 |
11 | 218750000 | 1.099998 | 40.366287 | QAM256 | 11 |
12 | 226750000 | 1.200001 | 40.366287 | QAM256 | 12 |
13 | 234750000 | 1.400002 | 40.946209 | QAM256 | 13 |
14 | 242750000 | 0.799999 | 40.366287 | QAM256 | 14 |
15 | 250750000 | 0.700001 | 40.366287 | QAM256 | 15 |
16 | 258750000 | 1.400002 | 40.366287 | QAM256 | 16 |
17 | 266750000 | 1.400002 | 40.366287 | QAM256 | 17 |
18 | 274750000 | 1.099998 | 40.366287 | QAM256 | 18 |
19 | 282750000 | 1.200001 | 40.366287 | QAM256 | 19 |
20 | 290750000 | 1.500000 | 40.366287 | QAM256 | 20 |
21 | 298750000 | 1.400002 | 40.366287 | QAM256 | 21 |
22 | 306750000 | 0.599998 | 40.946209 | QAM256 | 22 |
23 | 314750000 | 0.400002 | 40.366287 | QAM256 | 23 |
24 | 322750000 | 1.299999 | 40.946209 | QAM256 | 24 |
26 | 338750000 | 0.700001 | 40.366287 | QAM256 | 26 |
27 | 346750000 | 0.599998 | 40.366287 | QAM256 | 27 |
28 | 354750000 | 1.000000 | 40.366287 | QAM256 | 28 |
29 | 362750000 | 1.599998 | 40.366287 | QAM256 | 29 |
30 | 370750000 | 1.200001 | 40.366287 | QAM256 | 30 |
31 | 378750000 | 0.599998 | 40.366287 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 40.366287 | 0 | 0 |
1 | Locked | 38.605377 | 24 | 0 |
2 | Locked | 38.983261 | 39 | 0 |
3 | Locked | 38.983261 | 25 | 0 |
4 | Locked | 38.983261 | 15 | 0 |
5 | Locked | 40.366287 | 3 | 0 |
6 | Locked | 40.366287 | 1 | 0 |
7 | Locked | 40.366287 | 0 | 0 |
8 | Locked | 40.366287 | 2 | 0 |
9 | Locked | 40.366287 | 1 | 0 |
10 | Locked | 40.366287 | 0 | 0 |
11 | Locked | 40.366287 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.946209 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.366287 | 1 | 0 |
16 | Locked | 40.366287 | 1 | 0 |
17 | Locked | 40.366287 | 0 | 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 | 1 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 40.946209 | 0 | 0 |
26 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 40.366287 | 0 | 0 |
29 | Locked | 40.366287 | 0 | 0 |
30 | Locked | 40.366287 | 1 | 0 |
31 | Locked | 40.366287 | 1 | 0 |
33 | 94 | 4K | 1840 | QAM4096 | 424 |
33 | Locked | 43 | 0.5 | 4920247 | 6 |
on 24-03-2022 09:21
Time Priority Description
Thu Mar 24 05:28:25 2022 | 3 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 24 05:28:25 2022 | 3 | Unicast 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 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 24 05:32:25 2022 | 3 | Received 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 2022 | 3 | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 24 05:32:41 2022 | 3 | Unicast 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 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 24 05:33:50 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; |
on 24-03-2022 09:26
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 46.020599 | 5120 KSym/sec | 64QAM | 2 |
2 | 39400000 | 45.520599 | 5120 KSym/sec | 64QAM | 4 |
3 | 46200000 | 45.770599 | 5120 KSym/sec | 64QAM | 3 |
4 | 60300000 | 46.770599 | 5120 KSym/sec | 64QAM | 1 |
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 |
on 24-03-2022 09:33
@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
on 24-03-2022 09:34