NG Firewall Virtual Appliance on VMware: Difference between revisions

From Edge Threat Management Wiki - Arista
Jump to navigationJump to search
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Untangle can be virtualized through a [http://en.wikipedia.org/wiki/Virtual_appliance virtual appliance] running on [http://www.vmware.com VMware] ESX or ESXi.
NG Firewall can be installed as a virtual appliance in VMware for use in production environments or for learning and demonstration purposes.


The virtual appliance can also be used in for demonstrations in VMware player, workstation, fusion, or server, but it is not recommended run a production installation in these environments. Support will help with '''Untangle''' configuration but configuration of the virtualization hypervisor is beyond the scope of Untangle support.
=== Getting Started ===
 
:* '''Demo virtual appliance''': suitable for installation on a laptop or  desktop in order to have a working instance of the platform running inside your Window, OS X, or Linux OS for testing or demonstration purposes. This is supported using VMware Player, Fusion, Server, or Workstation and requires only one physical network interface.  Use this mode if you have only one physical network interface in your VMware host machine. 
:* '''Production virtual appliance:''' to be used as a network gateway.  This mode requires at least two physical network interfaces (three if you want or need an external DMZ).  We recommend you use either VMware ESX or ESXi Server.  Use this mode if you  have two or more physical network interfaces that you can connect to external, internal and (optionally) DMZ networks.
 
 
== Untangle Support and VMware ==
 
Untangle wants you to have a successful deployment. Unfortunately, our support staff doesn't have the expertise in VMware ESX to ensure that we can help you with installing and configuring VMware. We will certainly help you with your Untangle configuration, provided it's running on ESX.
 
That being said, we'd like to make you aware that systems like Untangle that require a lot of real time processing aren't great candidates for virtualization. VMware works by "time-slicing" the physical CPUs in the host system.  While the VMware server is off processing other virtual machines, the Untangle server is unable to process traffic. At the same time, network traffic continues to arrive. This traffic stacks up and presents itself to the Untangle VM as "bursty."  This exacerbates any high load issues that may be present. The exact threshold of where it will be unsuitable is hard to say.  It is a combination of traffic level, types of traffic, and user expectations.
 
'''In summary''': We do not recommend virtualizing Untangle. If you choose to install Untangle in a virtual environment, the support team will assist you with any issues related to the Untangle and its applications, but they will not help with virtualization set up/connectivity issues or issues caused by virtualization (high load, slow speeds, etc).
 
To ease deployment, Untangle provides a Virtual Application for VMware (OVA) with pre-compiled VM tools from the download page.
 
The OVA has no swap file the virtual machine be allocated sufficient memory for Untangle.
 
== How to install on ESX or ESXi ==
 
=== Before we get started ===


Requirements:
Requirements:


# VMware ESX server version 6.5.0 Update 3 or newer
# VMware ESX server version 6.5.0 Update 3 or newer
# One virtual NIC and vSwitch per Untangle Interface
# One virtual NIC and vSwitch per NG Firewall Interface


==== Download the Untangle Virtual Machine ====
==== Download the NG Firewall installer ====


* Download the Untangle Virtual Appliance here:  http://www.untangle.com/get-untangle/.
  1. Log into your [https://launchpad.edge.arista.com/ Edge Threat Management] account.
  2. Click GET STARTED > Software Downloads at the top right-hand corner.
  3. Download either version of the installer. Note that both options install the same software, however the "Serial" version uses only a command-line interface.  


==== Deploy OVA file to ESX server ====
==== Deploy image to ESX server ====
* Once the OVA file is downloaded, open your VMware vSphare Client and login to your server.
* Open your VMware vSphere Client and login to your server.
[[Image:vmware3.jpg|none|256px|vCenter Login]] 
* Create a new virtual machine and point the CD-Rom to the NG Firewall ISO image.
* Once you are logged in, click File -> “Deploy OVF Template…”
* Configure the CPU and RAM per the [[Hardware Requirements]] guidelines.   
[[Image:vmware4.jpg|none|128px|vCenter File->Deploy]] 
* In the “Deploy OVF Template” wizard mark “Deploy from file:” And hit “Browse…”
[[Image:vmware5.jpg|none|512px|vCenter Deploy Wizard 1]] 
* Browse to the location where you saved your OVA file and click "Open".
* Then hit “Next”
[[Image:vmware7.jpg|none|512px|vCenter Deploy Wizard 2]] 
* Read The Template Details and click “Next”.
[[Image:vmware8.jpg|none|512px|vCenter Deploy Wizard 3]] 
* In the “Name and Location screen” you may either change the name or leave it at the default. Click “Next”.
[[Image:vmware9.jpg|none|512px|vCenter Deploy Wizard 4]] 
* In the “Resource Pool screen” If you use Resource Pools, select the appropriate pool for the new Untangle VM and click "Next". Note: You can always move the VM to another Resource Pool after it's installed. 
[[Image:vmware10.jpg|none|512px|vCenter Deploy Wizard 5]]
* In the “Datastore screen” Select what datastore you want use click “Next”.
[[Image:vmware11.jpg|none|512px|vCenter Deploy Wizard 6]]  
* In the “Ready to Complete” screen, verify that everything looks OK and click “Finish”
* In the “Ready to Complete” screen, verify that everything looks OK and click “Finish”
[[Image:vmware12.jpg|none|512px|vCenter Deploy Wizard 7]] 
 
* Wait for the “Deploying” Progress Meter.
==== Configure Physical NIC to vSwitch mappings ====
[[Image:vmware13.jpg|none|256px|vCenter Deploy Progress Meter]] 
* When it is done, Click "Close".
[[Image:vmware14.jpg|none|256px|vCenter Deployment Completed]]
==== Verify/Configure Physical NIC to vSwitch mappings ====
* Setup/confirm your vSwitch Settings. Click on the ESX host, then select “Configuration" tab and "Hardware -> Networking”  
* Setup/confirm your vSwitch Settings. Click on the ESX host, then select “Configuration" tab and "Hardware -> Networking”  
[[Image:vmware19.jpg|none|512px|vCenter Hardware->Networking]]
[[Image:vm19.jpg|none|512px|vCenter Hardware->Networking]]
* It is best practice to place your  “Management Network “ is on a own vSwitch. (This is not a Must but if you can make sure that Untangle does not exist on the same vSwitch as any Management Interface)
* It is best practice to place your  “Management Network “ is on a own vSwitch. (This is not a Must but if you can make sure that NG Firewall does not exist on the same vSwitch as any Management Interface)
* On the vSwitches that Untangle will connect to activate “promiscuous mode” click on “Properties…”
* On the vSwitches that NG Firewall will connect to activate “promiscuous mode” click on “Properties…”
[[Image:vmware20.jpg|none|512px|vCenter vSwitch Properties]]
* Ensure that Promiscuous has status “Accept”  otherwise hit "Edit" and go to the “Security “ Tab and change “Reject” to “Accept”.  You will need to do this on all vSwitches that NG Firewall Virtual Machine connects to!
* Ensure that Promiscuous has status “Accept”  otherwise hit "Edit" and go to the “Security “ Tab and change “Reject” to “Accept”.  You will need to do this on all vSwitches that Untangle Virtual Machine connects to!
[[Image:vm21.jpg|none|512px|vCenter vSwitch Properties2]]
[[Image:vmware21.jpg|none|512px|vCenter vSwitch Properties2]]
 
==== Configure the Virtual Machine for your Network ====
==== Configure the Virtual Machine for your Network ====
* Right click on the new Virtual Machine and select “Edit  Settings”.
* Right click on the new Virtual Machine and select “Edit  Settings”.
[[Image:vmware15.jpg|none|256px|vCenter Edit Settings]]
[[Image:vm15.jpg|none|256px|vCenter Edit Settings]]
* You will need to add new virtual NICs and connect them to the appropriate vSwitches. Warning! Two Bridged Interfaces to the same vSwitch will crash your ESX server.  Each Untangle NIC should be connected to it's own vSwitch.  Each vSwitch should be connected to it's own Physical NIC, or at least be separated by VLAN tagging at the physical NIC level.
* You will need to add new virtual NICs and connect them to the appropriate vSwitches. Warning! Two Bridged Interfaces to the same vSwitch will crash your ESX server.  Each NG Firewall NIC should be connected to its own vSwitch.  Each vSwitch should be connected to it's own Physical NIC, or at least be separated by VLAN tagging at the physical NIC level.
* In this example, you can see that the new NICs are connected to different vSwitches labeled LAN and DMZ.   
* In this example, you can see that the new NICs are connected to different vSwitches labeled LAN and DMZ.   
[[Image:vmware17.jpg|none|512px|vCenter VM properties]]
[[Image:vm17.jpg|none|512px|vCenter VM properties]]
* Under “Options”->“VMware Tools” make sure to check the “Synchronize guest time with host” and click "OK"
* Under “Options”->“VMware Tools” make sure to check the “Synchronize guest time with host” and click "OK"
[[Image:vmware18.jpg|none|512px|vCenter VM properties/tools options]]
[[Image:vm18.jpg|none|512px|vCenter VM properties/tools options]]
==== Celebrate! You're at the end ====
Now you are ready to Power on your Untangle VM.
 
== More Info and Troubleshooting ==
 
For more information on the underlying issues, please see the following:
 
* Kernel documentation
* [http://www.vmware.com/support/pubs/ VMware documentation]
* [http://www.microsoft.com/technet/prodtechnol/virtualserver/2005/proddocs/default.mspx?mfr=true Microsoft Virtual Server documentation]
* [http://forums.untangle.com Untangle Community Support]
* [http://www.untangle.com/live-support Untangle Live Support]
For information about using your new Untangle software, see our [[Untangle Server User's Guide]].
 
Happy virtual Untangling!

Latest revision as of 15:59, 24 July 2024

NG Firewall can be installed as a virtual appliance in VMware for use in production environments or for learning and demonstration purposes.

Getting Started

Requirements:

  1. VMware ESX server version 6.5.0 Update 3 or newer
  2. One virtual NIC and vSwitch per NG Firewall Interface

Download the NG Firewall installer

 1. Log into your Edge Threat Management account.
 2. Click GET STARTED > Software Downloads at the top right-hand corner.
 3. Download either version of the installer. Note that both options install the same software, however the "Serial" version uses only a command-line interface.

Deploy image to ESX server

  • Open your VMware vSphere Client and login to your server.
  • Create a new virtual machine and point the CD-Rom to the NG Firewall ISO image.
  • Configure the CPU and RAM per the Hardware Requirements guidelines.
  • In the “Ready to Complete” screen, verify that everything looks OK and click “Finish”

Configure Physical NIC to vSwitch mappings

  • Setup/confirm your vSwitch Settings. Click on the ESX host, then select “Configuration" tab and "Hardware -> Networking”
vCenter Hardware->Networking
vCenter Hardware->Networking
  • It is best practice to place your “Management Network “ is on a own vSwitch. (This is not a Must but if you can make sure that NG Firewall does not exist on the same vSwitch as any Management Interface)
  • On the vSwitches that NG Firewall will connect to activate “promiscuous mode” click on “Properties…”
  • Ensure that Promiscuous has status “Accept” otherwise hit "Edit" and go to the “Security “ Tab and change “Reject” to “Accept”. You will need to do this on all vSwitches that NG Firewall Virtual Machine connects to!
vCenter vSwitch Properties2
vCenter vSwitch Properties2

Configure the Virtual Machine for your Network

  • Right click on the new Virtual Machine and select “Edit Settings”.
vCenter Edit Settings
vCenter Edit Settings
  • You will need to add new virtual NICs and connect them to the appropriate vSwitches. Warning! Two Bridged Interfaces to the same vSwitch will crash your ESX server. Each NG Firewall NIC should be connected to its own vSwitch. Each vSwitch should be connected to it's own Physical NIC, or at least be separated by VLAN tagging at the physical NIC level.
  • In this example, you can see that the new NICs are connected to different vSwitches labeled LAN and DMZ.
vCenter VM properties
vCenter VM properties
  • Under “Options”->“VMware Tools” make sure to check the “Synchronize guest time with host” and click "OK"
vCenter VM properties/tools options
vCenter VM properties/tools options
Retrieved from "https://wiki.edge.arista.com/index.php?title=NG_Firewall_Virtual_Appliance_on_VMware&oldid=28690"