...
| Note | ||
|---|---|---|
| ||
The instructions in this section are for the VMware VSphere® platform. For the OpenStack platform, refer to the Infoblox Deployment Guide for NetMRI and Operations Center. |
To configure the Remote Sandbox, do the following:
- Open the administrative shell.
- Download the Sandbox VM file from Infoblox using any scp program (such as WinSCP).
If you chose the OVF file type, the downloaded file contains an OVF file, a VMDK file, an MF file, a README file and a LICENSE file. The OVF file is what you will need to import into your VMware hypervisor. The MF file contains checksums of the OVF and VMDK files to verify that the exported files are correct before importing. The README file contains detailed instructions for deployment of the remote sandbox.
The standard VMX and VMDK files along with a README file and a LICENSE file, may also be deployed into VMware Workstation. You import the VMX file into the VMware hypervisor. The README file contains detailed instructions for deployment of the remote sandbox. Load the files into the hypervisor.
For example, In VSphere, choose File –> > Deploy OVF Template and select the file from the correct folder.
After the file loads, give the virtual machine a new name, choose where the VM is deployed, and choose its datastore.Note title Note The remote sandbox (VM) uses DHCP upon initial startup to acquire its IP configuration. You may change this value to static IP subnet and mask values through the Setup utility (see Step 7 below). Change the remote sandbox network configuration using the VMware console; avoid changing the sandbox configuration directly through an SSH connection. This prevents dropped SSH connections when the default DHCP configuration is changed to a potentially different static address in the Setup program.
...