You have the option to deploy Lumu Virtual Appliances as cloud collectors in cloud solutions such as AWS, Azure, and Google Cloud.
This guide contains the necessary steps to deploy a Lumu Virtual Appliance as a cloud collector on Microsoft Azure.
To ensure the successful deployment of a Lumu VA on Azure, you must meet the following minimum requirements:
In order to create a cloud collector, you need to download and import a Virtual Appliance into Microsoft Azure and create a Virtual Machine. This section walks you through using PowerShell to set up a Lumu VA on Azure.
1. Access the
Lumu Portal and navigate to the Virtual Appliance menu and select ‘Hyper V’ from the ‘Download for’ drop-down list. Unzip the file that contains the appliance image.
2. Download AzCopy 10 utility from the
Microsoft website, unzip and place the files on the directory:
3. Open a PowerShell console as an administrator and run the following command to install Azure prerequisites:
4. Run the following command on the PowerShell console to authenticate your Azure Account:
At the end of the setup process, you can rollback the policy using the command:
6. Upload the appliance image to Azure. You can upload the VHD file to Azure using the PowerShell or via Azure Portal.
To upload the VHD file, access to the Azure Portal and open the Storage explorer dashboard.
In the Storage Explorer, go to the Blob containers option and create a new one providing a name of your preference.
The next step is to upload the VHD file.
Finally, navigate to the Disks area of the Azure Portal and click to add a managed disk:
In the Create managed disk area, select your subscription, a resource group, enter a name, and select a region for the disk and adjust the other settings as necessary. When you're done, select Create.
To upload the VHD file using the PowerShell, prepare the Azure environment to host the Lumu Virtual Appliance using the following commands:
7. Create an Ubuntu server in Azure following Microsoft documentation. The virtual machine must be created in the same zone where the Lumu virtual appliance was uploaded.
Once you have configured Azure and uploaded the Lumu Virtual Appliance, you are ready to activate and explore the VA general settings.
9. Consult our
General Configuration guide for instructions on VA activation and set up.
Once you have the appliance activated and configured, set the Lumu VA as default DNS Server for name resolution.
10. Apply the new DNS servers to the current machines. Access your Azure Virtual Network settings and the list of virtual networks, select the virtual network for which you want to change DNS servers for, in this example “LUMUvnet935”.
11. Select “DNS servers” under “Settings” and add the internal IP Addresses of the Lumu Virtual Appliances you deployed on Azure as “Custom”.
If you change the DNS settings for a virtual network or virtual machine that is already deployed, the DHCP lease time may be longer than you expected. The DHCP is responsible for allocating IP addresses and other information to requesting clients.
For the new DNS settings to take effect immediately on existing servers, you must perform a DHCP lease renewal on all affected VMs in the virtual network. See
Flushing DNS Cache for guidance.
The final step is to verify that your DNS connections are correctly routed through Lumu. See Validate your DNS Settings for more information.