Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Aruba Mobility Master licence stacking

This thread has been viewed 10 times

  • 1.  Aruba Mobility Master licence stacking

    Posted Jun 21, 2019 05:03 AM
      |   view attached

    Hello can someone explain me on thing,


    I have a client which bought MM-VA-500 Mobility Master licence, but in the near future client is planning to setup more than  1200 APs.


    Question is: can I intall Aruba Mobility Master VM.ova using requirments for MM-VA-5K which are 10vCPU;64G RA;64G disk space. Than intall MM-VA-500 licence and when client exceeds MM-VA-500 limits add additional, lets say MM-VA-1k licence, and basically to have MM-VA-1.5k (MM-VA-500+MM-VA-1k)?

     

     



  • 2.  RE: Aruba Mobility Master licence stacking
    Best Answer

    Posted Jun 21, 2019 07:37 AM
    Yes it is possible on both questions

    Sent from Mail for Windows 10


  • 3.  RE: Aruba Mobility Master licence stacking

    Posted Jun 23, 2019 09:32 PM

    To add to Victor's response, for someone else that might read this and did not have the foresight to build the VM bigger at the start.

     

    In the ArubaOS VM documentation, there is a section on how to increase your flash disk size, so resizing can be done after the fact.

     

    If you do upgrade the flash after the fact, the procedure has you create a new disk, the ArubaOS will see the first disk SCSI 0:0 and the 2nd disk 0:1 as the current drives. It will see the new disk SCSI 0:2 as new, and copy the files from SCSI 0:1 to SCSI 0:2.

     

    The direction then tell you to delete the original disk, SCSI 0:1 (please follow the procedure, not my notes here).

     

    After the original disk is deleted, the SCSI addresses will be 0:0 and 0:2. You should rename SCSI 0:2 to SCSI 0:1.

     

    If you do not, it will not cause a problem. However, it you were to increase the disk size again in the future by repeating this procedure, you would have SCSI 0:0 and SCSI 0:2. If you were to create a new bigger disk, it would become SCSI 0:1. When you reboot, the MM will see the first two disks as the current system, SCSI 0:0 and the new blank SCSI 0:1, and your system will boot as if it has never been set up because the new SCSI 0:1 doesn't have any config. Don't fret, SCSI 0:2 should still be there (and of course you backed up your flash and snapshotted your VM).

     

    I hope this helps,