I am having some slowness with our VMM and not really finding any indication as to why - ie. all specs in the vSphere indicate it's not maxing out CPU/Memory/Disk/etc. I was thinking about rebooting it to see if it clears this up, but didn't want to risk any impact to APs/clients while it's down for 5-10 minutes.
Has anybody rebooted a mobility master (VM or Hardware) and confirmed this does not cause any disruption / outages at the controller/ap level?
Thanks for the feedback.
Thanks Victor - I don't think any of those services are in effect for us (minus AirMatch) so we should be OK for a single reboot window.
As with all things, snap a backup before rebooting. That is best practice for any production device **just in case for whatever possible reason it doesn't come back up**. In my house, which as far as my wife and daughter are concerned, I do a backup and snapshot in vsphere before reloading :)
Thanks all, I did reboot the VMM and had no issues during the reboot. The issue we were having seems to be VMWare related though, as I originally issued a reboot from within the ArubaOS and that did not resolve my connectivity issue. I then logged into vSphere and stopped the host machine and started it again, that corrected the issue and the VMM has been snappy and functional as it was before.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.