This is a utility VM used while deploying a scenario. The main purpose of this VM is to allow the scenario VMs to be configured via a network connection with the Administrative VM. The Administrative VM acts as a router so the scenario VMs can fetch files from Internet, if needed, usually during Phase 1.

The secondary purpose of the SetupVPN is to allow the transfer of files to and from the Administrative VM to a remote VirtualBox instance. Because VirtualBox does not allow the upload of files directly, as VMware does, any OVA, ISO, or IMG file that is required on a remote VirtualBox instance is transferred via this VM. It is also used for downloading exported VMs for packaging a newly developed scenario.

The setup VPN works slightly differently than the Runtime VPN System. The setup VPN's server is always the Administrative VM. It will bind to port 7890 on the address of it's eth0 interface (determined at run-time). Instances of the SetupVPN running on remote Hypervisors (which necessarily must be imported and configured manually, see below), must be able to contact the Administrative VM on that address and port.


Download available on the Downloads page


Installation of this VM is required on any remote Hypervisors that you wish to use. See the OccpAdmin page for how to specify and use multiple Hypervisors.

  • Create a new VM using the ISO from the download above.
  • Ensure that the VM has two interfaces, the first of which must be able to connect to the Administrative VM. This can be NAT or Bridged for VirtualBox, and a vSwitch assigned to an appropriate physical card for VMware ESXi.
  • Please ensure that this VM boots on each hypervisor before proceeding.

See Virtual Box Model 2 Install Guide for detailed instructions on using VirtualBox. VMware settings can be similar.