10-11-2012 05:59 AM - edited 10-11-2012 06:04 AM
I'm new to Aruba and I am testing a 105 in order to fault-find a problem a customer has using our hand-held computers when in an Aruba IAP environment. I have a 105 here which was working fine but after I upgraded the firmware to 220.127.116.11-18.104.22.168_35320 is is now showing the CPU at between 50% and 100% pretty much all the time. Previously it was sitting at about 5%-10%.
Previously I had a single network with a single client using WPA2 Personal but with the new firmware even with no networks we are still maxed-out.
I was looking to find either a reason for this huge CPU usage or a way to go back to an older versionof the firmware.
I should add that the AP is pretty much at default.
Does anyone have any ideas?
10-11-2012 08:04 AM
I have the same issue with IAP-105s in our lab. It appears to be intermittent (but frequent) and only on the IAP that is acting as the VC. After upgrade the GUI is very slow to unusable. A show cpu on the console shows the "user percentage between 45 and 99% utilization. Memory is consistant at 65-69mb free. Show log user provides no out of place errors.
I am using 2 IAP-105 ROW APs. One is over a wireless mesh. I am usually unable to access the network during this time. For me each episode has lasted between 3 and 30 minutes. I have tried reboots and factory resets. Even with a minimal config the issue persists. Downgrading to 22.214.171.124 does correct the issue. The issue did seem more difficult to reproduce with only one IAP.
10-11-2012 08:08 AM
That sounds exactly like the scenario I am seeing but with just one AP. The Web interface is almost unusable as it can take a minute just to refresh the page.
How did you manage to reflash the firmware as I don't seem to be able to find where the older versions are kept?
10-11-2012 08:28 AM
If the webUI is unusuable, you can upgrade using the CLI using any of the 3 protocols
FTP / TFTP / HTTP
An example of upgrading using tftp :
10-11-2012 08:17 PM
Disabled the MAS integration and check if this help. Goto Settings > MAS Integration > Disabled > Apply.
Share the "show cpu" output, Goto
Support > Show CPU Utilization > (Select the Access Point) > Run
10-12-2012 12:11 PM
It looks as if disabling MAS Integration is the key to dropping the CPU utilization here. It is now down to a more manageable 19% on average. It is still not as responsive as the old firmware was but the CPU running at 100% seems to have stopped.
Thanks everyone for the help.
10-12-2012 01:51 PM
I'm experienceing the exact same issue. I'm going to try disabing MAS integration as recommended. Let you know if it works for us as well.
10-15-2012 01:20 AM
I may have spoken too soon when I said that disabling MAS integration was the fix since I tried to connect to the AP this morning and it was running slow again with the CPU at 100% for most of the time. I found that MAS Integration had reset to being on again for some reason so I turned it off, but the Ap is still running slow with CPU usage running between 50% and 100%.
I think I will try taking the firmware version back down a level.
10-15-2012 01:47 AM - edited 10-15-2012 02:05 AM
This gets stranger by the minute. The CPU graph is showing the CPU utilization at 40% (see Capture1.jpg) but when I run the Support->AP CPU Utilization it shows it at about 99% idle.(see Capture2.jpg)
The lack of web interface response tends to suggest that the 40% is correct but why then should the ps (I'm assuming) output be saying 98% idle?
On another and possibly related note, it would appear that no matter what task you put in the Support->Command drop down box, when you press run it just gives the results of the AP CPU command (or possibly the first command it saw as that was what it was in this case).