To ALL:

   We also are moving to ArubaOS version 8.2.1.1 this summer, but we are a 
little further along.   We have 6,000 access points (as mix of 
214,215,314,315,325,324,205h,303h) and 8 7240 controllers.   We upgraded to the 
7420xm controllers and did a hardware appliance for the mobility 
master/standby.   We currently have 4 nodes up in a production cluster with 
about 3,000 ap’s on it. We are scheduled to complete the move by mid july.

For the most part it is working fine.    It takes a while to get used to the 
new design/commands/config.   We have found that there are still some bugs in 
the mobility master GUI and it is difficult to do certain things with the GUI.  
  We built the mobility masters from scratch and used 90% cli.   Most of the 
commands are the same as version 6.x so once you understand your hierarchy it 
is easy to move stuff over via the cli.    The cli is your friend.    We have 
ran into a bunch of issues configuring interfaces and port channels in the gui 
so that is all done via the cli.   We do configure vlans, vlan interfaces, etc 
via the gui.  Once everything was built I do most changes/tweaks via the gui 
(system profiles is the main area to work in) but I still build the VAP and 
WLAN via the cli as it is just too difficult to do in the gui.

We also had to re-organize/re-design the overall system to take advantage of 
the clusters.  I combined subnets, made them larger and spread them across all 
nodes in the cluster.  Airwave is another issue as there is no way to split 
clusters across airwave servers and we have two.   So we are going to end up 
with unbalanced airwave servers, one for each cluster.  We also bridge some 
wired vlans through the controllers to get the “experience” and that seems to 
be working fine (as long as you exclude the vlans from the cluster).

Airgroup seems to be your pain point in version 8 right now.   I have heard 
version 8.3 has a bunch of airgroup issues and we have a case called in for 
8.2.1.1 for airgroup.   We are trying centralized with Clearpass so your 
mileage may vary.   We also ran into a bug with clerapass sending down a timer 
with a coa, the timer would expire but the coa would not work, still open.

But all our users seem to be happy and work fine for the most part.   We are 
doing to stick with version 8 and hopefully get the few issues worked out 
before semester start.   I do feel this is the summer to do it.


From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
<[email protected]> On Behalf Of Harvard Townsend
Sent: Thursday, June 28, 2018 5:47 PM
To: [email protected]
Subject: [WIRELESS-LAN] Aruba version 8 (Mobility Master) and AP-115 access 
points

For those of you with Aruba wireless infrastructure, what are your experiences 
with running ArubaOS version 8.X plus the Mobility Master architecture with 
AP-115 access points? HPE/Aruba is telling us that model is supported 
(confirmed in the ArubaOS 8.2.0.0 release notes) and they are not aware of any 
issues. However, I heard from an Aruba reseller that a number of their 
customers, both commercial and higher ed, had significant issues when they 
upgraded to 8.X and moved to the mobility master architecture.  We purchased 
the MM license and want to make the jump to 8.2.1.1 from 6.5.3.4 this summer, 
but are hesitant given the rumor.  Have any of you experienced problems with 
AP-115s and Mobility Master?
Thanks,
--
Harvard Townsend
Director of Infrastructure & Security
Academic & Institutional Technology<http://www.wheaton.edu/ait>
Wheaton College, IL
Office:    630.752.5528
********** Participation and subscription information for this EDUCAUSE 
Constituent Group discussion list can be found at 
http://www.educause.edu/discuss.

**********
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

Reply via email to