"Mgmtringfullcount error" and AiCloud update

[CL-Jeremy]

(4/15) EDIT: Please try firmware version 3.0.0.4.360 for ASUS AiCloud and to stabilize wireless.

www.asus.com/Networking/RTN56U/#support_Download

______________

Hello Everybody!

I have a message from our support team regarding the RT-N56u and a problem that has been occurring. Please take the time to read it and let me know if you have any questions.

"Hi Everyone,

First of all, I would like to thank everyone supporting our RT-N56u router. The RT-N56u has been out for about two years and remains one of the top performing routers on the market. That said, we still have future updates coming to the RT-N56u’s firmware as well as some issues we are working to address.

The main issue I would like to address today is the “MgmtRingFullCount” error that is affecting some networking environments. I do apologize to everyone that has had this issue as this has been a long standing issue for some. This is a high priority and we’d like to resolve this as soon as possible. We need some help from users that are experiencing this error. I have been working with development on this issue for several months and we have not been able to reproduce the “MgmtRingFullCount” error consistently. I have several units from users that have this issue, but I cannot reproduce it easily. It is unlikely to be a hardware issue.

Here are the symptoms for the “Mgmtringfullcount” error”
-System log errors that show this repeating entry:
Feb 8 07:26:25 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=1!
Feb 8 07:26:25 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=2!
Feb 8 07:26:25 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=3!
-Loss of internet connection with all wireless clients
-Wireless status on Windows will show “Limited Connectivity”
-Wired clients remain unaffected and stays connected.

We have found this may be related to some clients going in or out of sleep/hibernate modes and IGMP snooping. We have re-added the IGMP snooping toggle in the UI as of firmware 3.0.0.4.334.

We would like more user data to help us resolve this issue as we cannot debug it properly without a reproducible environment. If you have this issue, we’d appreciate it if you contact us and provide the following information:
-Firmware version
-Full system log with the error included
-Settings file
-A list of the wireless clients in the network
-Network activities
-Observations during the time the error started occurring

Please send this information to Jeremy at cl-jeremy@asus.com.

I would also like to let everyone know that AiCloud is still coming for the RT-N56u. We do not currently have an estimated release date as the above issue has taken a high priority for the moment. We will be sure to update when we have more information on the release. Thank you for your patience.

-Adam"

 

[Zone15]

I don't have logs or anything right now because I think I found a workaround. I started having the errors after I enabled 40 MHz channel bandwidth. If I limit the router or laptop to 20 MHz, I get no errors.

 

[Slamb]

after 10 days it happend to me too next time i will send logs

 

[taedan]

I don't have logs or anything right now because I think I found a workaround. I started having the errors after I enabled 40 MHz channel bandwidth. If I limit the router or laptop to 20 MHz, I get no errors.

I have it set to 20 MHz and I still get these errors.

 

[baadnewz]

don't sweat too much about sending logs, when it comes to asus is just talk.

I've sent logs and so and didn't get any reply from CL-Jeremy

 

[kayakj]

don't sweat too much about sending logs, when it comes to asus is just talk.

I've sent logs and so and didn't get any reply from CL-Jeremy

They appear to be working on a solution. I have sent logs in the past they have responded with new beta firmwares for me to try and see if the firmware prevents the errors etc etc.. They are working on it too slowly ( considering how long this router has been on the market), but they are working on it

 

[CL-Jeremy]

don't sweat too much about sending logs, when it comes to asus is just talk.

I've sent logs and so and didn't get any reply from CL-Jeremy

I'm sorry it took me a while to respond. I hope you didn't have too much trouble over the weekend.

I can assure you that we are working on the problem and would appreciate any information anyone can provide about what they are experiencing.

 

[RogerSC]

don't sweat too much about sending logs, when it comes to asus is just talk.

I've sent logs and so and didn't get any reply from CL-Jeremy

That's really not fair...I've sent problems to Jeremy and he has always responded when he can. Just give him a while, I'm sure he's not just working on one problem at a time.

 

[baadnewz]

After I disabled ipv6

- no more "Mgmtringfullcount error"
- download speed improved from 72 mbps to 88 mbps
- router stopped freezing at high speed downloads.

 

[CL-Jeremy]

After I disabled ipv6

- no more "Mgmtringfullcount error"
- download speed improved from 72 mbps to 88 mbps
- router stopped freezing at high speed downloads.

Is this on the router? IPv6 is disabled by default, did you enable it previously then disable it?
Or is this on one of your clients?

 

[kayakj]

I think it was just chance that the errors stopped appearing when IPV6 was disabled. I get the errors and have not enabled ipv6 on the current setup since flashing/ clearing nvram. The two times I have tried the most recent firmware I initially got the errors in the first 10 minutes, and the next time it took about 3 days for the router to completely lock up with the errors.

 

[baadnewz]

Is this on the router? IPv6 is disabled by default, did you enable it previously then disable it?
Or is this on one of your clients?

on my router. yes is disabled by default and i did enable ipv6. after a while i disabled ipv6, all my issues gone (might be just luck )

 

[RogerSC]

I think it was just chance that the errors stopped appearing when IPV6 was disabled. I get the errors and have not enabled ipv6 on the current setup since flashing/ clearing nvram. The two times I have tried the most recent firmware I initially got the errors in the first 10 minutes, and the next time it took about 3 days for the router to completely lock up with the errors.

Yes, and I had IPv6 enabled and didn't see the errors.

 

[taedan]

It seems like I am getting these errors around the time I am streaming something (e.g., Netflix) through my iPhone. If I were to revert back to a 1.0.X firmware, which would you recommend?

 

[arul]

if u still wondering which 1.x to get. its definitely 1.0.1.7f, many user claim it to be the most stable.

 

[CL-Jeremy]

Hi Everybody!

The latest firmware version (3.0.0.4.360) has AiCloud implemented for the RT-N56u. Please try it and let me know if anybody has any problems with it.

Also, for the MgmtRing issue, this version does have a change in the drivers so please check this version for better stability.

www.asus.com/Networking/RTN56U/#support_Download

Thanks.