Wireless Access

All

Is there a list of AP config changes (currently on a Mobility Conductor environment running 8.10.0.14) that causes an AP to reboot?  Or more importantly that does NOT cause an AP to reboot?  We have some APs in a high density environment that are beginning to push the boundaries of mac client association of 64 and I'd like to bump that number up to 128.  Depending on the specific location, the APs are 335s, 535s, 635s, or 575s.  It would be easier if the APs do not reboot or bootstrap when I do this, but it it must I will plan around that.  Also, has anyone had any issues with bumping the max association up to 128?

Thanks

Jeff

Reboot should only occur when provisioning.  Bootstrap should be restricted to some of the settings in the AP system profile.

Changing settings in the SSID or VAP will probably result in a radio reset on the APs, potentially requiring all client devices to reassociate, but that should be almost hitless.

All

Is there a list of AP config changes (currently on a Mobility Conductor environment running 8.10.0.14) that causes an AP to reboot?  Or more importantly that does NOT cause an AP to reboot?  We have some APs in a high density environment that are beginning to push the boundaries of mac client association of 64 and I'd like to bump that number up to 128.  Depending on the specific location, the APs are 335s, 535s, 635s, or 575s.  It would be easier if the APs do not reboot or bootstrap when I do this, but it it must I will plan around that.  Also, has anyone had any issues with bumping the max association up to 128?

Thanks

Jeff

All

Is there a list of AP config changes (currently on a Mobility Conductor environment running 8.10.0.14) that causes an AP to reboot?  Or more importantly that does NOT cause an AP to reboot?  We have some APs in a high density environment that are beginning to push the boundaries of mac client association of 64 and I'd like to bump that number up to 128.  Depending on the specific location, the APs are 335s, 535s, 635s, or 575s.  It would be easier if the APs do not reboot or bootstrap when I do this, but it it must I will plan around that.  Also, has anyone had any issues with bumping the max association up to 128?

Thanks

Jeff

See the AOS CLI Guide.  

Page 9 - Commands That Rest the Mobility Conductor or AP. 

I believe that setting (Max Associations) is in the SSID Profile - which will cause an AP reset, according to the CLI Guide. 

We increased the Max Associations back in AOS 6.5.x. 

We used Airwave to track / alert based on APs that showed, "AP is resource constrained" messages, which (I believe) were how they indicated they couldn't serve additional clients due to the Max Associations Limit.  Although I had initially considered limiting the scope to APs in HD (High [client] Density) areas, I ultimately ended up applying the update to Max Associations to our primary SSID.  

I believe, I ultimately made this change overnight || during a scheduled maintenance window & we've carried forth the configuration in AOS 8.10.x. 

We had no issues increasing Max Associations to 128.  At that time, the bulk of our deployed APs were AP-225 & AP-325s (but included 105s, 125s, & 135s as well). 

Best of luck, 

-Raf

------------------------------
Rafael Hinojosa

Original Message:
Sent: Oct 30, 2024 10:16 AM
From: johnstonj@rowan.edu
Subject: Max client Association and AP reboot question

All

Is there a list of AP config changes (currently on a Mobility Conductor environment running 8.10.0.14) that causes an AP to reboot?  Or more importantly that does NOT cause an AP to reboot?  We have some APs in a high density environment that are beginning to push the boundaries of mac client association of 64 and I'd like to bump that number up to 128.  Depending on the specific location, the APs are 335s, 535s, 635s, or 575s.  It would be easier if the APs do not reboot or bootstrap when I do this, but it it must I will plan around that.  Also, has anyone had any issues with bumping the max association up to 128?

Thanks

Jeff