Configuring your Virtual Appliances (VAs)
Previously, we brought up the ESX or Hyper-V Console to view your newly provisioned Virtual Appliances (VAs). Once you've opened the virtual machine, you'll see a command screen that looks like this:
From the console after a brief boot up process, you are prompted to configure the DNS forwarder by tabbing between fields.
For the Name field, this is the Name that will appear next to the managed VA in your Umbrella dashboard. It may help you to include the IP address in the Name for ease of reference.
For the IP, Netmask and Gateway fields, give the VA a static IP on the same network / site as you’d like to manage with the VAs along with the appropriate netmask and gateway for that network.
For the Local DNS 1 and 2 fields, enter your local DNS servers, which are often the IP addresses of your Windows Servers with both the Active Directory Domain Services and DNS Server roles installed.
Finally, press Return, then Tab to ‘Save’ and press Return.
Note: All VA time zones are GMT +0.
You should see a sync message indicating that the VA and the Umbrella service are communicating.
If you receive error messages or would like to to know more about what each of test is, you can tab to the test and hit Return.
The information here can help you understand what possible network issue could exist between the VA and the Umbrella secure cloud gateway. In this example, the SSL test to the host 'disthost.opendns.com' on port 443 timed out. If you were unable to complete the tests, please check the ESX or Hyper-V network configuration to ensure you've matched it properly.
Once you've identified and resolved the issue, the tests continue to run in the background and the test will subsequently succeed without intervention. If you'd like to ensure the tests are run successfully, you can reboot the VA by going to the System Menu (CTRL+S).
Assuming the tests were completed without error, the next step is to verify the Virtual Appliance syncs within your dashboard.
When you return to the dashboard, navigate to Settings > Sites and Active Directory. You should see your VAs listed with the name you gave it earlier in the VA Console configuration.
Your first VA has been provisioned successfully.
To Create the Redundant Virtual Appliance
- Repeat the above steps to create a secondary Virtual Appliance, which is required for continuous operation.
- Set up the Redundant VA as the secondary DNS server for your network in the IP settings for the DHCP scope being given to clients (or static IP if your configuration requires that.)
Note: A secondary VA ensures 100% uptime in the event of any critical issues, as well as, enabling auto-upgrades to stagger any necessary reboots. Depending on your setup, you can place each VA on a separate VMware or Hyper-V host. Please make sure you deploy the secondary virtual appliance by following the steps, do not clone the already deployed virtual appliance onto a new one.
Next, we can look at setting up the routing of local DNS zones and giving your VAs a proper name in your local DNS.