Wireless Access

 View Only
  • 1.  Setup virtual Mobility Master - Memory versus FlashDisk / Disk space allocation

    Posted Nov 08, 2018 10:22 AM
      |   view attached

    We want to upgrade from Version 6.5.4.2 to Version 8.2.2.1. We are in process to install a new virtual mobility master. Now we are struggling with the sizing of the virtual machine memory size versus FlashDisk and Disk space. We get an error message after startup of the virtual machine that we should decrease memory or enlarge FlashDisk space (please see attachment). Can somebody please help us to determine the settings of the Virtual Mobility Master. We are deploying a Aruba OVA template. There are 2 Disks preconfigured. For us it's not clear how mutch RAM / versus disk space on disk 1 and disk 2 we must assign for a mobility Master with 550 Licenses. We assume we must setup a MM for 1000 Devices, does mean MM-VA-1K, correct? How much memory, Disk1, Disk2 we should assign in the virtualization?

     

    Thanks for any help

    Attachment(s)



  • 2.  RE: Setup virtual Mobility Master - Memory versus FlashDisk / Disk space allocation

    Posted Nov 08, 2018 12:08 PM

    Hi,

    you are right, AOS Virtual Appliance Installation Guide is not very clear about the disk sizes, especially for disk 1.

    I looked through all the isntallation variants for the different hypervisors. For me most consistent is:
    - RAM: as shown in Sizing table
    - Disk 1: 4 GByte
    - Disk 2: as shown in Sizing table
    Compare "Installing ArubaOS ISO Using vSphere Hypervisor". Here disk one is 4 GByte. For disk 2 there is a link to the sizing table.
     

    You are right. Sizing is listet for up to xxx devices from license.
    So MM-VA-500 is for up to 500 APs.
    You should choose MM-VA-1k.

    This leaves you with sizes:
    - vCPU's: 8
    - RAM: 32 GByte
    - Disk 1: 4 GByte
    - Disk 2: 32 GByte

    I installed several MMs with disk 1 of 4 GByte and never had issues while updating. (started with 8.0)

    Regards, Jö

     



  • 3.  RE: Setup virtual Mobility Master - Memory versus FlashDisk / Disk space allocation

    Posted Nov 09, 2018 05:32 AM
      |   view attached

    Hi Jö

     

    Thank you for your answer. Our virtualization team has now setup controller according the specs for the MM-VA-1k, does mean vCPU's: 8, RAM: 32 GByte, Disk 1: 4 GByte, Disk 2: 32 GByte. We got still the same error message. Reading the error message carefully we identified that we have don' t have problem with the Flash memory (it's only a warning) the software is complaining about the amount of CPU's. (pls. see attached error message)

     

    If we leave the original OVA parameter unchanged, does mean vCPU's: 3, Disk 1: 4 GByte, Disk 2: 8 GByte, the system is coming up without any problems. Should we deploy the virtual machine with the original parameters and change disk space and CPU's afterwards?

     

    Best regards

    Marcello

     



  • 4.  RE: Setup virtual Mobility Master - Memory versus FlashDisk / Disk space allocation
    Best Answer

    Posted Nov 09, 2018 06:35 AM

    Hi,

     

    you need to assign the cpus, so that just one socket is used.

     

    older vSphere Client:

    2018-11-09 12_30_00-vCPUs.png

     

    Newer vSpehere (Web) Client:

    2018-11-09 12_30_00-vCPUs2.png

     

    Regards, Jörg

     

     



  • 5.  RE: Setup virtual Mobility Master - Memory versus FlashDisk / Disk space allocation

    Posted Nov 09, 2018 09:38 AM

    Hello Jörg

     

    Yeaa!!  That was helping, the servers are now coming up. With your hint I was able to find another poste covering the same topic, link below:

    https://community.arubanetworks.com/t5/Wireless-Access/Deploying-ArubaOS-8-MM-on-VMware-virtual-CPU-sockets-cannot-be/td-p/299763

     

    Give Kudos, thanks for supporting

    Marcello



  • 6.  RE: Setup virtual Mobility Master - Memory versus FlashDisk / Disk space allocation

    Posted Mar 04, 2021 07:06 AM
    There is no reply button on the post, only reply privately button active.
    Sorry have to reply you directly.

    My question is after fix the virtual CPU socket to 1 , the MM boot up without any problem.
    The "FLash size (5GB) should be at least ......" warning message no longer appear?

    Thanks.

    tckoon

    ------------------------------
    Choh Koon Tan
    ------------------------------