How to Deploy a SecureEdge VTx on Proxmox

To install SecureEdge virtual appliances or machines on a Proxmox VE server, you must obtain the necessary ISO, OVA, VMDK, or KVM images for your guest OS.

Before deploying the Barracuda SecureEdge VTx unit, verify that the host system meets the minimum storage requirements and review the resource recommendations for the production system.

The virtual machine (VM) must be configured with five ports to avoid encountering a box activation error. Note that while not all ports need to be unique, Port 1 (P1) must be linked to a separate Virtual Network (Vnet) to facilitate High Availability (HA) pairing. The remaining ports can be connected to the default vmbr0 bridge.

Before You Begin

For information on the sizing of your CPU, disk, and RAM, see Virtual Systems (VTx) Deployment.
Download the Barracuda SecureEdge VTx appliance OVA image from the Barracuda Download Portal.
Currently, VM disk uploads are not supported. You can import virtual machines using the command line. For more information, see QEMU/KVM Virtual Machines

You need root access to the Proxmox environment.

Step 1. Create a Directory for the Files

Access the Proxmox environment via Shell in the web UI or via SSH using an external application like PuTTY or MobaXterm.
In the root home directory, create a directory. For example, in this case, the directory name is “ova”.
mkdir ova cd /ova
Create additional directory for the appliance you will deploy.
mkdir vtx

Step 2. Upload the Files

Download the OVA files and extract their contents to upload the necessary files for the virtual machine. You can do this in two ways:

(Option) Step 2a. Download via Browser and Upload to Proxmox

Go to the Barracuda Download Portal https://dlportal.barracudanetworks.com and log in with your existing Barracuda Cloud Control account.
In the left menu, click Firmware and search for the ova files.
Select the appropriate product to download. Click the Download button at the bottom of the page.
Launch an application that supports file transfers and connect to the Proxmox server via SSH. Here, MobaXterm is used.
In the File Management pane, go to the directory you have created in Step 1.
Select the Upload File icon in the top left.
In the Windows Explorer window, go to the OVA’s download location on your local machine and select Open. Note: You will then see the file uploaded to the Proxmox Server. It may take some time.

(Option) Step 2b. Download Directly to the Proxmox Host

Obtain the OVA file URL from the Barracuda Download Portal.
- Go to the desired product OVA in the Download Portal.
- Right-click the Download button and select Copy Link.
Connect to the Proxmox host via SSH or open the Shell in the web UI.
Change the directory to the folder created in Step 1.
cd /ova/vfx
Use wget or curl commands to download the file.
wget -O [Local_Filename.ova] [Download_Link] wget -O vtx_v10.ova https://dlportal.barracudanetworks.com/download/6296/GWAY-10.0.1-0153-VTxxx.ova curl -o [Local_Filename.ova] [Download_Link] curl -o vtx_v10.ova https://dlportal.barracudanetworks.com/download/6296/GWAY-10.0.1-0153-VTxxx.ova

Step 3. Prepare the Image File

Create the qcow2 Disk Image

After uploading the files to the Proxmox environment, extract the OVA files and convert the disk image.

Unzip the OVA file using the tar command.
tar -xvf [Local_Filename.ova] tar -xvf vtx_v10.ova
Convert the vmdk file to the qcow2 format.
qemu-img convert -f vmdk -O qcow2 [Your_VMDK_File_Name.vmdk] qemu-img convert -f vmdk -O qcow2 GWAY-10.0.1-0153-VTxxx-disk1.vmdk cuda-VTx.qcow2

Step 4. Create a New Virtual Machine on Proxmox

Once you have a workable disk image file, create a ‘shell’ VM to apply it.

To create a new virtual machine within the Proxmox web UI, click Create VM.
In the General tab, specify values for the following:
- Name – Enter a name.
- VM ID – Enter a unique VM ID. Note: Take note of the VM ID used for the deployment.
In the OS tab, specify values for the following:
- Select Do not use any media on the OS tab.
- Type – Select Linux from the drop-down menu.
- Version – Select 6.x-2.6 Kernel from the drop-down menu.
In the System tab, keep the defaults and click Next.
In the Disks tab, delete the automatically created disk.
Complete the deployment according to the hardware requirements for the appliance.
In the final Confirm tab, verify that all values are correct, and then click Finish.

Step 4. Import Disk Image to your Virtual Machine

Go back to the console via SSH or Shell.
Return to the directory where the qcow2 file was created.
Use the qm disk import command to import to the VM.
qm disk import [VM ID] [Your_qcow2_File.qcow2] local-zfs --target-disk [Disk ID] qm disk import 201 cuda-VTx.qcow2 local-zfs --target-disk scsi0
After importing the disk to the VM, enable it in Boot Options and set its priority.
- To edit the boot order, select your VM, go to Options > Boot Order and click Edit.
- The Edit Boot Order window opens. Set the priority and ensure that the scsi0 device is enabled in the device list.

After the import completes, start the virtual machine and open the console to view the boot menu for your initial deployment. The Barracuda SecureEdge VTx unit boots. The appliance connects to the SecureEdge service and applies the configuration set in How to Create a T/VT Site Configuration in Barracuda SecureEdge.

Additional Information

List of commands used for quick reference:

curl -o [Local_Filename.ova] [Download_Link]
wget -O [Local_Filename.ova] [Download_Link]
tar -xvf [Local_Filename.ova]
qemu-img convert -f vmdk -O qcow2 [Your_Extracted_Filename.vmdk] [Converted_Filename.qcow2]
qm disk import [VM_ID] [qcow2_Filename.qcow2] local-zfs --target-disk scsi0