Virtual Box Model 2 Install Guide

This guide installs Virtual Box using a partially distributed model.

Basic Requirements

  • All machines to be used as a hypervisor will need to have a static IP address.
  • Administrative rights will be needed to change firewall settings on machines running VirtualBox web services.

Primary Hypervisor

  1. Install Virtual Box on each machine you will use in your OCCP deployment. The primary hypervisor is the machine that will host the VSN of a scenario.
  2. Install the Administrative VM
    1. Download the AdminVM on the Downloads Page
    2. Import the OVA file into your hypervisor using the VirtualBox import appliance tool option.
    3. Ensure that the first Network Adapter is connected to an interface that can reach the Internet. The interface must be in Bridged mode.
    4. Ensure that the second Network Adapter is connected to an "Internal Network" named OCCP_Setup
    5. Ensure that both Network Adapters are using the Adapter Type "Intel PRO/1000 MT Desktop "
    6. Create a folder on your host computer at C:\OccpShared\
      This folder will be where you store scenarios. This folder's full path will be known as the Import Directory.
    7. Edit the VM settings - Add this folder as a shared folder to your VM and make sure to select Auto Mount

Remote/Lab Machines

  1. Install Virtual Box on each machine you will use in your OCCP deployment.
  2. Install the SetupVPN VM on remote/lab machines.
    Each lab machine that will run a Player VM will require the installation of the SetupVPN VM.
    1. Download the SetupVPN ISO file on the Downloads Page
    2. Create a new virtual machine.
      • Name the virtual machine SetupVPN exactly as spelled.
      • Set the type to Linux
      • Set the version to Other Linux (32-bit)
      • Memory size 256 MB
      • Do not add a virtual hard drive
    3. Move the downloaded setupvpn.iso file into the new virtual machines folder. This location is usually in the users home directory.
    4. Edit the virtual machine and change the following settings
      1. Change Storage > CD/DVD and Choose a virutal CD/DVD disk file select the setupvpn.iso in the virtual machines directory, also check the Live CD/DVD option
      2. The first network interface must be able to connect to the Administrative VM. Bridged or NAT mode will work for this interface. The VM will acquire a DHCP address automatically.
  3. Create a folder on your host computer at C:\OccpShared\
    This folder will be where any deployed VMs are stored on the remote machine. This folder will be automatically mounted when needed.

Common Settings

All physical machines will need to have VirtualBox web services enabled on them. These services need to be started manually each time the machine is rebooted.

C:\<VirutalBoxInstallDirectory>\vboxwebsrv -H 0.0.0.0 -A null

Note: Check the VirtualBox documentation for how to use real authentication mechanisms with web services.

Linking Remote Machines

The process of linking remote machines to the primary hypervisor will require several steps. Launch the Admin VM and log into the console. The default username is occpadmin and password is 0ccpadmin Run the following commands using the occpadmin application.

  • Create the hypervisors.xml file using the addhv and delhv commands given to the occpadmin application.
    • Add your primary hypervisor using the machine's physical address.
      occpadmin --mode addhv --hvtype vbox --hvname primaryVSN --url http://<address>:18083 --importdir C:/OccpShared
      
    • Add each remote machine using the physical address for each machine in your lab setup.
      occpadmin --mode addhv --hvtype vbox --hvname lab1 --url http://<address>:18083 --importdir C:/OccpShared --remote
      ...
      occpadmin --mode addhv --hvtype vbox --hvname lab10 --url http://<address>:18083 --importdir C:/OccpShared --remote
      
  • Create a hypervisor map file in the occpadmin home directory
    nano mapfile
    
    • This file will need to be modified for each scenario deployed.
    • The file is a plain text file with one hypervisor per line. Each virtual machine that is part of a scenario needs to be specified on some line. Refer to the specific scenario for guidance on modifying the map file.
    • For a basic deployment configure the first line with the primary hypervisor name and a static IP address on your physical network. The address needs to be routable and not collide with any existing machines, the gateway is specified after the address.
    • On each additional line specify each of the player machines that you are going to use.
      primaryVSN/<address>,<gateway>: Router, vm1, vm2
      lab1: player1
      lab2: player2
      

After completing the steps outlined here a basic lab setup is complete. You can now download an available scenario and follow it's specific install instructions.