Wireless Access

Since upgraded to 6.3.1.0 from 6.3.0.0 I'm starting to see more and more AP-125s rebooting according to Airwave. This is the AMP event message: Device has rebooted: Change in number of reboots detected (got 3, expected 2).

At the time of the message there were 12 clients connected pushing about 1 Mb of traffic. I don't see anything in the graphs that would of indicated a problem. CPU utilization is around 44% and memory utilization looks to be averaging 81%. I"m not sure what those numbers were at the time of the reboot.

There were notices regarding the AP-125 with clients exceeding 70 but that will propably never be the case for our APs. Is anyone else noticing a problem with the AP-125s on 6.3.1.0?

We are aware of this and expect a patch for 6.3.1.1 coming out shortly.  For a workaround today, you can downgrade to 6.2.

I'm currently utilizing the centrallized licensing and have AP 225s in service. If I'm not mistaken those aren't supported on 6.2 code. I was under the impression that the 125 issues were fixed in 6.3.0.2. The caveat under remarks only mentions the following:

"ArubaOS 6.3.1.0 is not recommended for customers with AP-120 Series APs that routinely see over 70 clients associated to an AP. Please contact support if you have any questions."

Perhaps it shoulid be updated with the information you provided?

Are there any other changes that could be made? With several of the AP125s I've also had to manually reboot them when one particular user was unable to connect. Is this also part of the problem? Could you post what exactly you are aware of with the 120 series APs?

Thanks.

Try running this command to see if it is rebooting or bootstrapping a lot from the controller perspective :

show ap debug counters ap-name <apname>

We tested 6.3.1.0 with AP125's and didn't experienced reboots 

What's your bootstrap threshold value , default is 8. You can try increasing it to 15

Those utilization numbers are pretty normal for the AP125 now , I see those numbers even on 6.2.1.3 with barely any devices associated to the AP

100.3.2-linseypool-ground            LinseyPool-100            10.66.65.122   0            AP:HT:11/9/20.5      1            AP:HT:36/21/21       125

Peak CPU Util in the last one hour
----------------------------------
Timestamp                  CPU Util(%)   Memory Util(%)
--------- ----------- --------------
2013-10-23 08:51:06          20              80

You should probably open a ticket with TAC too

---

@victorfabian wrote:

 

 

Try running this command to see if it is rebooting or bootstrapping a lot from the controller perspective :

 

show ap debug counters ap-name <apname>

 

We tested 6.3.1.0 with AP125's and didn't experienced reboots 

 

What's your bootstrap threshold value , default is 8. You can try increasing it to 15

 

Those utilization numbers are pretty normal for the AP125 now , I see those numbers even on 6.2.1.3 with barely any devices associated to the AP

 

100.3.2-linseypool-ground            LinseyPool-100            10.66.65.122   0            AP:HT:11/9/20.5      1            AP:HT:36/21/21       125

 

Peak CPU Util in the last one hour
----------------------------------
Timestamp                  CPU Util(%)   Memory Util(%)
--------- ----------- --------------
2013-10-23 08:51:06          20              80

 

You should probably open a ticket with TAC too

 

 

---

The threshold is still at default. I'll try it at 15. What's the worst case for changing this that it takes longer to make the reboot decision when it's not reaching the controller?

It looks like I'm seeing roughly 2 reboots for the APs in question after the upgrade to 6.3.1.0.

You should test that with test ap-group to make sure it doesnt impact every AP on campus , you might be experiencing some packet loss on your network and if you see that the AP stop bootstrapping afte that change you may have to look into your network to see if there's any issues.

Do you see any crash on the APs and a lot bootstrapping ?

---

@victorfabian wrote:

 

You should test that with test ap-group to make sure it doesnt impact every AP on campus , you might be experiencing some packet loss on your network and if you see that the AP stop bootstrapping afte that change you may have to look into your network to see if there's any issues.

 

Do you see any crash on the APs and a lot bootstrapping ?

---

No Crash and Boostraps is at 1. I'm opening a TAC case to see what my options are. I didn't have the problem with 6.3.0.0 so I may be downgrading.

Your SE can give you reasonably accurate information on the release date for 6.3.1.1.  

FYI, It's release plan is pretty close...you may consider holding steady for that.

JF