Aruba Mobility Controller and Conductor in EVE-NG
Aruba's Virtual Mobility Controller and the Mobility Conductor are pre-installed in your CloudLabBox workspace. Use them to practise ArubaOS 8 controller configuration and its managed hierarchy.
Choose a planCheck it in the free demo
- Vendor
- Aruba
- In Add Node
- 10 images
- Templates
arubaclbarubamm- Newest
aruba-VMC-8.12.0.2-90468
Installed versions
Every Mobility Controller and Conductor name in the Add Node image list, exactly as you’ll pick it.
Started in our checksEach links to the tested tip below.
Template aruba
Virtual Mobility Controller
aruba-VMC-8.12.0.2-90468aruba-VMC-8.11.0.1-85785aruba-VMC-8.8.0.3_83072aruba-VMC-8.8.0.1_80393aruba-VMC-8.6.0.4-74969aruba-VMC-8.5.0.13_80140aruba-VMC_8.4.0.3aruba-VMC_8.3.0.3
Template clbarubamm
Mobility Conductor 8.12
clbarubamm-arubamm-8.12.0.3-91078clbarubamm-arubamm-8.12.0.2-90468Started in our checks
Add it to a lab
In Add Node, choose the template, then the image. The template fills in these settings; change them before you start the node.
| Image | Template | CPU | RAM | Interfaces | Console |
|---|---|---|---|---|---|
| Virtual Mobility Controller | aruba | 3 | 4096 MB | 7 interfaces | VNC |
| Mobility Conductor 8.12 | clbarubamm | 3 | 6144 MB | 3 interfaces | VNC |
EVE-NG admits a node by the CPU and RAM set on it, so a running node counts against your plan at these values. The largest of these templates starts nodes at 3 vCPU and 6,144 MB, which fits the free demo’s 6 vCPU and 8 GB, so you can start one there and open its console.
A Mobility Conductor with two managed controllers
Bring up the Conductor first, add two Virtual Mobility Controllers as managed devices, and push WLAN and user-role configuration down the hierarchy. There are no access point images, so the lab stops at the controllers.
Both the controller and the Conductor open with a VNC console.
- 1×Mobility Conductor 8.12
clbarubamm3 vCPU, 6144 MB - 2×Virtual Mobility Controller
aruba3 vCPU, 4096 MB each
Added with these defaults, the lab uses 9 vCPU and 14 GB of RAM. The smallest plan that fits is Standard, with 12 vCPU and 16 GB: £5 a day, or £1.25 an hour On-Demand.
Licences are yours to bring
ArubaOS 8 needs Aruba licences for access points and features, and CloudLabBox doesn't provide them. As the node tip says, provide the entitlements your controllers and access points need.
The images run only inside your CloudLabBox workspace; they aren’t available to download.
Questions about Mobility Controller and Conductor
What are Aruba Mobility Controller and Conductor?
The Aruba Virtual Mobility Controller runs ArubaOS 8 for wireless controller labs. The Mobility Conductor (formerly Mobility Master) manages a group of those controllers.
What's the difference between a Mobility Controller and the Mobility Conductor?
A Mobility Controller serves access points and users. The Mobility Conductor, formerly Mobility Master, manages a group of controllers and pushes their configuration down to them.
Which controller build matches the Conductor?
aruba-VMC-8.12.0.2-90468 is the same build as the Conductor image clbarubamm-arubamm-8.12.0.2-90468. Aruba expects a Conductor to run the same or a newer release than the controllers it manages.
Aruba Mobility Conductor: which profile should I choose?
Use the dedicated Mobility Conductor profile for the retained arubamm 8.12 images: 3 CPUs, 6 GB RAM, three network adapters and both supplied disks. The required single-socket CPU layout is applied automatically. arubamm-8.12.0.2-90468 reached the ArubaMM-VA initial setup dialogue. Complete setup and provide the entitlements needed for your controllers and access points. This is separate from the Aruba virtual mobility-controller profile.
Which Mobility Controller and Conductor images are installed?
10 images (8 Virtual Mobility Controller, 2 Mobility Conductor 8.12), all listed on this page exactly as Add Node shows them. The newest is aruba-VMC-8.12.0.2-90468.
How much CPU and RAM does a Mobility Controller and Conductor node use?
When you add one, the aruba template adds 3 vCPU and 4096 MB of RAM; the clbarubamm template adds 3 vCPU and 6144 MB of RAM. You can change both in Add Node, and your plan counts what each running node is set to.
More images
CloudLabBox is independent of the vendors named on this page. Their names identify the images in the workspace’s Add Node list.