AIMESH Network Stability

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

dasdfarmer

New Around Here
Greetings,

I recently created an AIMESH network with AX11000 as the Main node and 2 AX6100's as mesh nodes. All nodes are running the latest stock firmware. My current internet provided is Spectrum and I am using their modem for internet connection.

The system performs much better than my previous AIMESH system but it tends to crash once or twice a day. The Symptoms when it crashes are system suddenly can't get IP addresses. Rebooting all of the routers seems to clear it up.

I looked at the log for this mornings event and found a large number of the following messages right before it crashed:
Jun 21 09:08:22 kernel: CONSOLE: 064051.127 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.138 wlc_ap_authresp: status 0
Jun 21 09:08:22 kernel: CONSOLE: 064051.138 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.138 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>
Jun 21 09:08:22 kernel: CONSOLE: 064051.139 HWA1x RxPATH: Got rph count 0, pending_rph_req<0>

I did an internet search on these messages and did not find any hits.

Any advice on how to identify the problem and or fix it would be appreciated.

Best Regards
 

Adooni

Regular Contributor
at forum you can find same (I do not want to write a lot) posts about AiMesh challenges like for example https://www.snbforums.com/threads/aimesh-network-crashing-dropout.68347/

Can you tell if you have AiMesh Node connected wi-fi or cable. When it is not working Nodes are disconnected?

I like when people are very positive "The system performs much better than my previous AIMESH system but it tends to crash once or twice a day" - if crash 1or2 time a day is big improvement I do not want to ask what was before :)
 

dasdfarmer

New Around Here
at forum you can find same (I do not want to write a lot) posts about AiMesh challenges like for example https://www.snbforums.com/threads/aimesh-network-crashing-dropout.68347/

Can you tell if you have AiMesh Node connected wi-fi or cable. When it is not working Nodes are disconnected?

I like when people are very positive "The system performs much better than my previous AIMESH system but it tends to crash once or twice a day" - if crash 1or2 time a day is big improvement I do not want to ask what was before :)
Thanks for the input. I will review the information in the link you provided.

When I indicate that the new mesh system performs better than the previous. I was referring to network speeds. The previous network was slow in the places in my house that were the farthest from the nodes. The new system has consistent good speeds everywhere in my house. The old system didn't crash much, maybe once or twice a month.

The nodes are connected via wireless back haul.

Best Regards
 

leerees

Senior Member
The AX6100 had lots of problems with earlier firmware. It's definitely worth doing the following to eliminate them as the cause or your issue...

Update the firmware on your AX6100's. Afterwards, you must do a hard reset. It's a pain but it has to be done.
 
Last edited:

dasdfarmer

New Around Here
The issues you are describing are well documented and were due to problems with earlier firmware. To fix....

Update the firmware on your AX6100's. Afterwards, you must do a hard reset. It's a pain but there's no way round it. After that, the issues will be gone.
Thanks for the advice,
I am running the latest firmware on the AX6100's and They have both been reset as follows:
1. Remove them as nodes
2. Pressed reset button until the power light flashed
3. Added them again as nodes.

Should I do the hard reset via the WPS method?

Best Regards
 

leerees

Senior Member
Thanks for the advice,
I am running the latest firmware on the AX6100's and They have both been reset as follows:
1. Remove them as nodes
2. Pressed reset button until the power light flashed
3. Added them again as nodes.

Should I do the hard reset via the WPS method?

Best Regards
Definitely, the reset button method is not a hard reset

ASUS router Hard Factory Reset - Method 2

1. Turn the router off.
2. Press and hold the "WPS" button and turn the router on.
3. Power light is on (keep holding the WPS button).
4. Release the WPS button after the power light is off.
5. Reboot your router by manually pressing the power button.


[Wireless Router] ASUS router Hard Factory Reset | Official Support | ASUS Global
 

dasdfarmer

New Around Here
I did a hard reset last night on the 2 AX92u's and 3 hours later we had a crash. In this case, rebooting the AX92u nearest to us fixed the issue. In the past we have been rebooting all of the routers when the event occurs.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top