Looking to test waters in 8.7 soon will likely keep most MD on 8.5.0.10 - and as mentioned Aruba gives the green light to this:
But we've got 93H's we still need to support... so 8.2.2.9 is in this mix - working fine with MM on 8.5.0.10 anyone have experience with any MD's ~ 8.2.x under an 8.7.x MM? Travis Schick UCDavis Network Operations Center On Wed, Oct 14, 2020 at 8:00 AM Jonathan Waldrep <[email protected]> wrote: > On 2020-10-13 21:50:52-00:00, Kevin Grover wrote: > > We got some AP-575's not realizing they needed 8.7 code. Anyone > > running 8.7 in production? Any issues? > > Yes and yes. > > A little context. We've been running 8.7 somewhere in production since > July. In production, we've got a pair of ArubaMM-HW-10Ks for redundant > masters, and 18 MDs of various models and most of them in clusters. > > We were running 8.7 in the lab (which served our office at the time) > since 8.7 was in beta with no issues. > > Then we put 8.7.0.0 in production (mid July). > > The first issue we noticed was logging. Sometimes the controllers will > log (to syslog) a trace on the AMON process. We could not find a way to > disable this in config. Between all of our controllers, we saw up to > 20,000 logs per second. We ended up adding a rule to the syslog server > to drop anything with "amon_sender_proc" or "amon_recvr_proc". > > Then students came back. > > In the first 3 days, we had 5 kernel panics. After that, we downgraded > our 3 main clusters (12 MDs) to 8.5.0.10. This is supposed to be fixed > in 8.7.1.0, which just came out last week. I've got it running in the > lab, but haven't done any proper testing yet. > > We also seemed to have issues with an MD just refusing associations and > other connectivity issues. However, most of those were in the first few > days of class, and we definitely had other red herrings (Zoom and Canvas > decided to have issues the first day of class), so I don't have as good > of a definition on those problems. > > Oh, If your clusters are connecting the MM over v6, then the cpsec > whitelist doesn't sync. You'll have to whitelist any new APs on each MD > in the cluster. Or just keep using v4 for now. > > > In all, I would hold off on going to 8.7 for another release or 2. And > definitely roll out the deployment in stages. We currently have 8.7.0.0 > on our MMs, and some clusters on 8.5.0.10. This is a supported > configuration. You may want to leverage this to bring in your standalone > controller under your MM (you will need to upgrade the MM). > > On 2020-10-13 22:23:15-00:00, Cody Ensanian wrote: > > We went from 8.5.0.5 to 8.7.0.0 a few weeks ago (dual-MD cluster). > > After APs pulled their new image, they could not find the controllers > > (via the usual dns / resolving aruba-master). 1600 APs across campus > > down - just great. A quick band-aid fix was to push the master IP via > > dhcp scope option 43. > > We were already doing controller discovery based on DHCP options, so we > didn't see this. > > -- > Jonathan Waldrep > Network Engineer > Network Infrastructure and Services > Virginia Tech > > ********** > Replies to EDUCAUSE Community Group emails are sent to the entire > community list. If you want to reply only to the person who sent the > message, copy and paste their email address and forward the email reply. > Additional participation and subscription information can be found at > https://www.educause.edu/community > ********** Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the person who sent the message, copy and paste their email address and forward the email reply. Additional participation and subscription information can be found at https://www.educause.edu/community
