Thanks for your complete and clear answer.
Original Message:
Sent: Jan 13, 2024 08:12 AM
From: mkk
Subject: Updating Mobility Master
Agreed with Carson, updating the Mobility Conductor don't have much impact on clients, other than airgroups, ucc, airmatch (conductor tasks).
Some extras:
- Create a VMware snapshot of the Mobility Conductor appliance.
- Create a configuration backup of the Mobility Conductor.
- Upgrade to latest Long Support Release (LSR), which is currently AOS 8.10.0.9.
- Read the release notes carefully, also see if all hardware is supported. Link here.
------------------------------
Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
Original Message:
Sent: Jan 12, 2024 09:42 AM
From: chulcher
Subject: Updating Mobility Master
Rebooting the Mobility Conductor will not have significant impact on the network. The MCR is responsible for handling AirGroup when using the centralized setup so rebooting your only MCR when using AirGroup might have impact.
Note, if you are running the MCR as a virtual machine, you can install a second MCR virtual appliance and setup HA for the pair.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Jan 11, 2024 09:15 AM
From: gh.as
Subject: Updating Mobility Master
Hello,
We have plan to update our Mobility Master from 8.6.0.9
to last version,
We have cluster with 2 controllers(7502) with 155 APs such as: 315,345 and 535
and we have to increase flash space in VM
so:
I would like to know is it possible to do these actions without impact our controllers and APs?
in other word, If I reboot MM is impact our controllers??? for some reasons, we have to do it in working day,
Thanks for your help,
Best