12-18-2021 04:07 PM
12-22-2021 07:27 AM
01-27-2022 02:04 PM
01-27-2022 05:56 PM
rharris1962 wrote:
I currently have a mesh network running with 3 ASUS Routers.
GT-AXE11000 - Primary Router
RT-AX88U - AiMesh Node
RT-AC88U - AiMesh Node
I contacted ASUS via chat. They opened up a case for me and had me change some settings. This did not help.
My routers are connected by ethernet. Once I reboot my GT-AXE1000 router everything reconnects. I looked at the logs but can not find a reason why this is
happening. I have been using ASUS routers for 20 yrs and this is the first time I have had this issue. I saved off the logs
in case ASUS wanted them. Any suggestions would be appreciated.
Thanks
02-21-2022 05:17 PM
rharris1962 wrote:
I currently have a mesh network running with 3 ASUS Routers.
GT-AXE11000 - Primary Router
RT-AX88U - AiMesh Node
RT-AC88U - AiMesh Node
I contacted ASUS via chat. They opened up a case for me and had me change some settings. This did not help.
My routers are connected by ethernet. Once I reboot my GT-AXE1000 router everything reconnects. I looked at the logs but can not find a reason why this is
happening. I have been using ASUS routers for 20 yrs and this is the first time I have had this issue. I saved off the logs
in case ASUS wanted them. Any suggestions would be appreciated.
Thanks
03-13-2022 02:43 PM
Enter the following two cmds after telnet to router
nvram set log_size=2048
nvram commit
Then manually restart the router
The next time user encounters a router crash, submit a new GUI FBF and let us know the crash of the approximate time frame.
To get the setting file: step. Administration -> Restore/Save/Upload setting, and you will find the [save setting] step3. click button
[save] And provide to us the CGF file that will be saved.
To get the system log step1. login router step2. System Log -> General log, you will find[save]button here step3. click button[save]
A. May disable the
smart connect
feature for selected models (Most AX series, GT-AC5300, RT-AC5300, RT-AC3100, RT-AC88U, RT-AC3200)
B. 2.4GHz connection issues:
1. Change the' (Wireless -> General -> Band = 2.4GHz)
*
2. Change channel bandwidth to '40 MHz' (Wireless -> General -> Band = 2.4GHz)
*
3. Change control channel to 1, 6, or 11 (Wireless -> General -> Band = 2.4GHz) (l = lower band, u = upper band)
*
*
C. 5GHz connection issues:
1. Wireless -> General -> 5GHz-1 or 5GHz-2 -> Select 'Legacy', 'N only' or 'N/AC mixed' in Wireless Mode
2. Change channel bandwidth to '40 MHz' (Wireless -> General -> Band = 5GHz-1 or 5GHz-2)
*
3. Change control channel (Wireless -> General -> Band = 5GHz-1 and 5GHz-2 [for Tri-band models] )
*
*
4. May try to disable 'Airtime Fairness' option from GUI > Wireless > Professional
*
To get the setting file:
step1. login router goes to Administration->System->Change the router login name to admin and password to asus1234 then proceed
to step 2.
step2. Administration -> Restore/Save/Upload setting, and you will find the [save setting]
step3. click button[save]
And provide to us the CGF file that will be saved.
To get the system log
step1. login router
step2. System Log -> Gernel log, you will find[save]button here
step3. click button[save]
Do provide serial numbers and firmware versions for all AiMesh nodes. If the problem still
persists, please help verify make/model of the device(s) and MAC address(es) of the device that\u2019s having connection issue. (example:
Asus UX435 notebook, MAC address: aa:bb:cc:dd:00) And help suggest the customer to download and fill out the general topology form
(Download (doc): http://goo.gl/HGbozB or shorturl.at/nrvzZ) of the network layout, such as [ modem -> router -> Node 1, Node 2 client]
Make/Model and MAC address(es) of device(s) having the issue (may list 1 - 3 devices, or state all devices are having issue)
Please help verify make/model of some of the devices are being used and having problem with the router.
In addition, we want to confirm whether this problem occurs under Aimesh. May set the AX92U to ethernet backhaul or reset the AX92U
to repeater mode or router mode to see if the problem still occurs.
In addition, the user has many devices. Is there a way for the user to provide a simple network topology confirmation? Probably know
how the user connects the devices.
04-16-2022 05:51 PM
jerzor wrote:
Hi everyone, here's a follow up for my original post:
TLDR: Nothing has been fixed yet with the GT-AXE11000 and a lot of time has been wasted. Jump to the end of this post to get recommended steps out of the way.
Long version:
After my original post I contacted support and eventually arranged for a replacement under warranty when none of their troubleshooting did anything useful. I had my older GT-AX11000 as a backup while the exchange was happening. The GT-AX11000 was plugged in, configured to match my network settings so all devices would connect seamlessly, updated to the latest firmware, and immediately went back to having the problems that prompted me to buy the GT-AXE11000 thinking (incorrectly as it turns out) that it would solve the problems. I contacted support about this, was hopeful they would look into these problems, and eventually was ghosted by Asus until I point blank asked what had happened with that case and was told because it was out of warranty they refused to touch it. Oh well, I just toughed it out until my replacement GT-AXE11000 arrived.
The replacement GT-AXE11000 came and I plugged it in, configured it to match my network settings so all devices would connect seamlessly, updated to the latest firmware, and immediately went back to having the problems that the first GT-AXE11000 had. After several more rounds with support I was told that basically all of the feedback and logs I've submitted for a year were useless to them (specifically, even though I almost always submitted feedback on the spot after crashes/disconnects, this is a quote from them: "e also need the user to submit a GUI feedback form immediately after the router crash & reboot. We checked several system logs and found that the logs were washed out and no related information can be found. We checked several system logs and found that the logs were washed out and no related information can be found.") After that they suggested the following, so for anyone else facing this problem you may as well do this and get it over with in advance:
After doing that it took a few weeks for the next crash to occur (twice crashing/disconnecting in a single week after a few weeks of no crashing) and I'm now waiting on them to get back to me after submitting that latest feedback. I've also updated to the newest firmware after the second issue (3.0.0.4.386_47875-g7b7d10a) and we'll see if it's improved anything.
Along with the above log step, here are some pointers:
They seem to have shuffled who responded to my case continually, so I had a lot of people keep asking me for information I'd already given. I've had them tell me they can't review the history. They have been blatantly wrong when telling me that the router uptime resetting was in fact my ISP's problem and disconnects on the ISP's side were just a minor problem causing this number to reset, not the ASUS router crashing. They also push their chat service in the emails, which has invariably ended with me being given a case number and told I'd be contacted by email after a support escalation, so the chat step is only worth doing exactly once to get a case number in the system and get the email ball rolling. Use the case number liberally every time you submit feedback through the router administration page and in contact with them so they don't lose track. If they offer replacement under warranty, it's worth biting the bullet and immediately taking them up on it and going through the hassle just to get it out of the way. After they see the problems occur with the brand new replacement, that will get the case escalated as a systemic problem, not a one-off hardware problem.
Here's a complete list of everything I've been asked for in emails, which I suggest you just stick in a big text file and folder of files and copy paste (along with your case ID) every time you get contacted by the support staff, it'll save you some time:
(This one above I ignored because I had repeatedly told them the whole router was crashing, not just random wireless hiccups, and I certainly wasn't going to go in and change network information for almost half of the devices that would get cut off if I split the SSIDs)
(You'll notice the one above contradicts an earlier troubleshooting step, not sure why they suddenly told me to start changing the router login details before sending them this)
(They weren't happy with me only giving information for the GT-AXE11000 and my RT-AX92U even though I had repeatedly told them that it was the router itself crashing and all my devices were getting disconnected, so I'm definitely not going to write down dozens of MAC addresses beyond the ones I gave)
(After this one I sucked it up and typed out the dozens of devices on my network, routers, modems, switches, PCs, phones, tablets, smart devices, and even the ethernet hardware on custom built devices)
(I had repeatedly told them it's a mixture of devices floating between the router and the AI Mesh router, but in this email I told them at least which devices were hardwired)
I was also continually sent requests to fill out their "Wireless Feedback Form", the most recent copy of which I can't attach to this forum post because it says the only allowed filetypes are jpgs, go figure.
I'm not sure why most of this information isn't getting through to them no matter how many boxes and debug logs I select in the router administration page for feedback, but again, oh well. If you can package all this up and shoot it to them in one go, hopefully that's several email rounds fewer you have to deal with them. I'll see if I can keep this thread up to date on what their next steps are. Clearly there's something systemically wrong both with the router line itself and the analysis going into troubleshooting.
04-26-2022 04:24 AM
richard.d.sun wrote:
Any update? My GT-AXE11000 crashes every week. I have 3 right now set up in a mesh, just redid everything again and the crash repeats itself, once in a while one of the mesh nodes crashes, but when the main node crashes, then when it's a big hassle.
04-26-2022 04:33 AM
04-27-2022 07:22 AM