Deploy using vCenter Server and ESXi - BlueCat DNS Edge

DNS Edge Deployment Guide

prodname
BlueCat DNS Edge

This section gives detailed instructions for deploying a DNS Edge Service Point using vCenter Server and ESXi.

Prerequisites

The following prerequisites must be met before you begin:
  • You have an operational vCenter Server.
  • vCenter Server already has a datacenter.
  • You have an operational ESXi deployment.
  • vCenter Server and ESXi are able to contact each other.
  • You have an OVA file for a Service Point image.
    Note: Avoid spaces in the service point image filename.
Attention: You must deploy a new Service Point from an OVA file. Do not clone a Service Point from an existing VM, as the cloned Service Point will fail to register with the DNS Edge Cloud.

VMware compatibility

The following table lists hypervisors that are compatible with DNS Edge, along with three different methods for deploying the service point image on each hypervisor:

vCenter v5.5 v6.0 v6.5 v6.7
vSphere web client

(Method 1)

Not applicable Requires VMware Client Integration Plugin installed and a compatible browser (supports NPAPI). For setup instructions, see http://www.opvizor.com/get-the-client-integration-plug-in-running-in-vsphere-web-client-6-x/.
  1. Deploy the OVA service point image as a new virtual machine and don't power it on.

    The web client doesn't recognize the .iso that's packaged within the OVA bundle. You must mount it explicitly as outlined in the subsequent steps.

  2. Extract the files from the OVA bundle.
    This can be performed using an archive utility or through the command line. If you are using Linux, use the following command:
    tar -xvf servicePointImage.ova
    The following files are extracted from the OVA bundle:
    service-point.ovf
    service-point.mf
    service-point-coreos.vmdk
    service-point-iso.iso
  3. Upload the .iso file using the Datastore Browser.
  4. Edit the VM settings and select CD/DVD drive.
  5. Select the Datastore ISO File Device Type and browse to the uploaded .iso file.
  6. Ensure that the Connect at power on option is selected.
  7. Power on the service point virtual machine.
ovftool

(Method 2)

Run the following command with ovftool:

./ovftool --acceptAllEulas -ds="{datastore_name}" ~/{path_to_service_point_image}.ova vi://{vCenter_IP}/{vCenter_Datacenter_name}/host/{ESXi_IP}

You will be prompted for a user name and password for vCenter.

vSphere desktop client

(Method 3)

  1. Select File from the top bar and click Deploy OVF Template....
  2. Select your OVA file and complete the instructions in the wizard.
The desktop client is no longer supported on VMWare v6.5 or v6.7.
ESXi v5.5. v6.0 v6.5 v6.7
ESXi Embedded Host Client

(Method 1)

Not supported
  1. Deploy the OVA service point image as a new virtual machine and don't power it on.

    The web client doesn't recognize the .iso that's packaged within the OVA bundle. You must mount it explicitly as outlined in the subsequent steps.

  2. Extract the files from the OVA bundle.
    This can be performed using an archive utility or through the command line. If you are using Linux, use the following command:
    tar -xvf servicePointImage.ova
    The following files are extracted from the OVA bundle:
    service-point.ovf
    service-point.mf
    service-point-coreos.vmdk
    service-point-iso.iso
  3. Upload the .iso file using the Datastore Browser.
  4. Edit the VM settings and select CD/DVD drive.
  5. Select the Datastore ISO File Device Type and browse to the uploaded .iso file.
  6. Ensure that the Connect at power on option is selected.
  7. Power on the service point virtual machine.
ovftool

(Method 2)

Deploy the .ova SP image into the ESXi host:

./{path to ovftool}/ovftool -dm=thin --net:"NAT"="{ESXi_network_name}" -ds={datastore_name} ./{path to SP image}/{servicepointImage}.ova "vi://{username}:{password}@{your ESXi host's ip address}"

vSphere desktop client

(Method 3)

  1. Select File from the top bar and click Deploy OVF Template....
  2. Select your OVA file and complete the instructions in the wizard.
The desktop client is no longer supported on VMWare v6.5 or v6.7.