Skip to content
VEX-NXDocs

Get started

Install the OVA

Import VEX-NX into VMware Workstation or ESXi, complete first boot, and reach the web sign-in.

OVA install path
OVA install path

The OVA install is automatic. A correct import already contains Disk 1, Disk 2, and a cidata CD; you only confirm they are there before the first power-on.

What you need

ItemDetail
FileThe single vex-nx-<version>.ova, not a partial OVF folder
VMware WorkstationVersion 14 or later
ESXi / vSphere6.5 or later (7 and 8 supported). ESXi 6.0 is not supported
Nested virtualizationNeeded for QEMU labs; see System requirements
BrowserCurrent Chrome, Edge, or Firefox

Note

The OVA is tens of gigabytes. Keep it on local disk with plenty of free space, and verify its SHA-256 checksum from the download page first.

VMware Workstation

  1. Prepare the Windows host. For QEMU labs, turn Hyper-V off and reboot.
  2. Import. Choose File → Open, select vex-nx-<version>.ova, and accept the wizard. Raise RAM and CPU now if you already know you need bigger labs.
  3. Keep the three adapters in order. Adapter 1 is Management (typically Bridged), adapter 2 is Internet for lab egress (NAT), adapter 3 is the isolated Lab network (Host-only). Remap them if all three landed on Bridged.
  4. Check settings before first power-on. Under Processors, enable VT-x/EPT and CPU performance counters. Confirm Hard Disk 1 (about 40 GB), Hard Disk 2 (about 53 GB, do not remove), and the cidata CD with Connected on.
  5. Power on and watch the console. Within about two minutes, a management network menu appears: press 1 for DHCP (the default) or 2 for a static address. Do not power off during first-boot install.
  6. Open the web UI. Browse to http://<management-ip>/ and sign in as admin / vexnx. You will set a new password.

ESXi and vSphere

  1. Prepare port groups. Create or choose three: Management, an uplink for internet egress, and an isolated lab network.
  2. Get the OVA onto the host reliably. Browser upload of a large file often fails with A required disk image was missing. Copy the .ova to a datastore with SCP, or deploy with ovftool:
bash
ovftool --acceptAllEulas --datastore=datastore1 --network=VLAN93 vex-nx-2.0.0.ova vi://user@esxi-host/
  1. Deploy. Choose Create / Register VM → Deploy a virtual machine from an OVF or OVA file, select the single .ova, and map the three networks in order. Do not power on yet.
  2. Run the mandatory check. In Edit settings, confirm Hard Disk 1, Hard Disk 2, the cidata CD Connected, three adapters in order, and Expose hardware assisted virtualization on.
  3. Size it. Raise from the 4 vCPU / 8 GB minimum before heavy labs.
  4. Power on and open the console immediately. Choose DHCP or static at the menu, wait for the hostname VEX-NX, then browse to the management IP.

Warning

If you see only one hard disk after import, the import is incomplete. Delete the VM and deploy again from the full .ova. Don't try to build Disk 2 by hand.

Default sign-in

AccessUserPassword
Web UIadminvexnx
SSHvexnxvexnx

Both force a password change on first use.

If it fails

SymptomFix
A required disk image was missingRedeploy the full .ova with ovftool or a datastore copy.
Console shows vex-nx-bake login:The cidata CD didn't apply. Power off, connect the OVA's cidata ISO, power on. If still stuck, run sudo cloud-init clean --logs with the CD connected and reboot once.
No DHCP/Static menuConfirm two disks and cidata Connected, then watch the console from the first seconds.
No management IPCheck the Management port group and DHCP; run ip a on the console (usually ens160).
QEMU nodes won't startNested virtualization is off. Enable it and power-cycle the VM.
FRR needs a pull on StartThe offline seed is still loading or DNS is wrong. Wait, or run sudo vexnx-seed-docker.

Next: First login.