The Aruba Mobility Master provides a 64-bit virtualized software-based managed platform on VirtualMachine (VM) architecture.
Mobility Master is the centralized management platform for deployment in a virtualized network infrastructure. The Mobility Master operates on VM platforms in VMware environments and can reside withother virtualized appliances.
NOTE: Aruba does not recommend over subscription of processors, memory, and NIC ports on the virtual machine.
Listed below are some of the advantages of switching to a Mobility Master:
The Mobility Master reduces the number of devices occupying rack space and the overheads associatedwith managing and servicing products from different vendors.
Multiple services are consolidated on a common platform, there by reducing the cost and optimizing the infrastructure by providing consolidated services.
Additional devices can be deployed remotely, increasing hardware selection option and flexibility.
By eliminating a single point failure, user can create a reliable and high-performance networking system.
On successfully installing the Mobility Master, refer to the ArubaOS 8.0.x Quick Start Guide for steps to setup the network
System requirements
Listed below are the minimum hypervisor host system requirements for ArubaOS to run as a guest Virtual Machine (VM) and the resources required for the VM to be functional:
Quad-core Core i5 1.9 GHz processors with hyper threading enabled.
8GB RAM
Minimum 2 physical NICs on the ESXi host
ArubaOS VM requirement
Listed below are the minimum resources required for the ArubaOS VM to function:
3 vCPUs.
4GB Memory.
10GB Disk space.
4 Virtual NICs.
The hypervisor host should not be oversubscribed in terms of number of VMs configured on a host as itadversely impacts the functionality and performance of ArubaOS. In instances where more than one VM issetup in a hypervisor, then:
The number of logical processors reported on the ESXi (vSphere client) should be higher or equal to the sumof vCPUs allocated to each of the VMs setup in that host.
The sum of the memory allocated to each VM should not exceed the overall host memory capacityreported.
The total CPU utilization, memory usage, and network throughput should not exceed 80% of the hostcapacity.
One NIC is shared with ESXi Management and the second is reserved for data path.
Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models. Hewlett Packard Enterprise believes in being unconditionally inclusive. Efforts to replace noninclusive terms in our active products are ongoing.
Was this information helpful?
Thank you!
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] lightningout:client-error:script-setup:https://support.hpe.com/connect/l/%7B%22mode%22%3A%22PROD%22%2C%22dfs%22%3A%228%22%2C%22app%22%3A%22c%3AdceLightningOutApp%22%2C%22loaded%22%3A%7B%22APPLICATION%40markup%3A%2F%2Fc%3AdceLightningOutApp%22%3A%22735_l5zZavnUSgq9PpC7BsVM2Q%22%7D%2C%22styleContext%22%3A%7B%22c%22%3A%22other%22%2C%22x%22%3A%5B%223%22%2C%22SLDS%22%2C%22isDesktop%22%5D%2C%22tokens%22%3A%5B%22markup%3A%2F%2Fforce%3AsldsTokens%22%2C%22markup%3A%2F%2Fforce%3Abase%22%2C%22markup%3A%2F%2Fforce%3AformFactorLarge%22%5D%2C%22tuid%22%3A%22KBpz0MjwkpOWRH7ZNXsSqA%22%2C%22cuid%22%3A-477949688%7D%2C%22pathPrefix%22%3A%22%2Fconnect%22%7D/app.css?3=