NG Firewall Virtual Appliance on VMware - Revision history

Bcarmichael: /* More Info and Troubleshooting */

2024-07-24T15:59:50Z

More Info and Troubleshooting

← Older revision		Revision as of 15:59, 24 July 2024
Line 36:		Line 36:
	* 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:vm18.jpg\|none\|512px\|vCenter VM properties/tools options]]		[[Image:vm18.jpg\|none\|512px\|vCenter VM properties/tools options]]
	~~== 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 Edge Threat Management Community Support]
	* [http://www.untangle.com/live-support Edge Threat Management Live Support]
	~~For information about using your new NG Firewall software, see our [[NG Firewall Server User's Guide]].~~

Bcarmichael: /* Celebrate! You're at the end */

2024-07-24T15:59:27Z

Celebrate! You're at the end

← Older revision		Revision as of 15:59, 24 July 2024
Line 36:		Line 36:
	* 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:vm18.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 NG Firewall VM.~~

	== More Info and Troubleshooting ==		== More Info and Troubleshooting ==

Bcarmichael: /* Verify/Configure Physical NIC to vSwitch mappings */

2024-07-24T15:57:09Z

Verify/Configure Physical NIC to vSwitch mappings

← Older revision		Revision as of 15:57, 24 July 2024
Line 20:		Line 20:
	* 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”

	==== ~~Verify/~~Configure Physical NIC to vSwitch mappings ====		==== 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:vm19.jpg\|none\|512px\|vCenter Hardware->Networking]]		[[Image:vm19.jpg\|none\|512px\|vCenter Hardware->Networking]]
Line 27:		Line 27:
	* 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 NG Firewall Virtual Machine connects to!
	[[Image:vm21.jpg\|none\|512px\|vCenter vSwitch Properties2]]		[[Image:vm21.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”.

Bcarmichael: /* Deploy image to ESX server */

2024-07-24T15:56:53Z

Deploy image to ESX server

← Older revision		Revision as of 15:56, 24 July 2024
Line 19:		Line 19:
	* Configure the CPU and RAM per the [[Hardware Requirements]] guidelines.		* Configure the CPU and RAM per the [[Hardware Requirements]] guidelines.
	* 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”
	* When it is done, Click "Close".
	==== Verify/Configure Physical NIC to vSwitch mappings ====		==== 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”

Bcarmichael at 15:55, 24 July 2024

2024-07-24T15:55:49Z

← Older revision		Revision as of 15:55, 24 July 2024
Line 1:		Line 1:
	NG Firewall 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 '''NG Firewall''' configuration but configuration of the virtualization hypervisor is beyond the scope of Edge Threat Management 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.


	== ~~NG Firewall Support and VMware~~ ==

	Arista Edge Threat Management 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 NG Firewall configuration, provided it's running on ESX.

	That being said, we'd like to make you aware that systems like NG Firewall 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 NG Firewall server is unable to process traffic. At the same time, network traffic continues to arrive. This traffic stacks up and presents itself to the NG Firewall 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 NG Firewall. If you choose to install NG Firewall in a virtual environment, the support team will assist you with any issues related to the NG Firewall and its applications, but they will not help with virtualization set up/connectivity issues or issues caused by virtualization (high load, slow speeds, etc).

	~~== How to install on ESX or ESXi ==~~

	~~=== Before we get started~~ ===

	Requirements:		Requirements:
Line 24:		Line 8:
	# One virtual NIC and vSwitch per NG Firewall Interface		# One virtual NIC and vSwitch per NG Firewall Interface

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

	* Download the NG Firewall Virtual Appliance:		1. Log into your [https://launchpad.edge.arista.com/ Edge Threat Management] account.
	1. Log into your Edge Threat Management account.		2. Click GET STARTED > Software Downloads at the top right-hand corner.
	2. Click GET STARTED 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.
	3. ~~Select~~ the ~~latest~~ version ~~and download the ISO file~~.

	==== Deploy image to ESX server ====		==== Deploy image to ESX server ====
	* ~~Once the image is downloaded, open~~ your VMware vSphere 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:vm5.jpg\|none\|512px\|vCenter Deploy Wizard 1]]~~
	* Browse to the ~~location where you saved your~~ image ~~and click "Open".~~
	* Then hit “Next”
	~~[[Image:vm7.jpg\|none\|512px\|vCenter Deploy Wizard 2]]~~
	* Read The Template Details and click “Next”.
	~~[[Image:vm8.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:vm9.jpg\|none\|512px\|vCenter Deploy Wizard 4~~]]
	* In the “Resource Pool screen” If you use Resource Pools, select the appropriate pool for the new NG Firewall VM and click "Next". Note: You can always move the VM to another Resource Pool after it's installed.
	~~[[Image:vm10.jpg\|none\|512px\|vCenter Deploy Wizard 5]]~~
	* In the “Datastore screen” Select what datastore you want use click “Next”.
	~~[[Image:vm11.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:vm12.jpg\|none\|512px\|vCenter Deploy Wizard 7]]~~
	* Wait for the “Deploying” Progress Meter.
	~~[[Image:vm13.jpg\|none\|256px\|vCenter Deploy Progress Meter]]~~
	* When it is done, Click "Close".		* When it is done, Click "Close".
	~~[[Image:vm14.jpg\|none\|256px\|vCenter Deployment Completed]]~~
	==== Verify/Configure Physical NIC to vSwitch mappings ====		==== 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”

Bcarmichael at 19:19, 23 January 2024

2024-01-23T19:19:39Z

← Older revision		Revision as of 19:19, 23 January 2024
Line 60:		Line 60:
	* 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)		* 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…”		* On the vSwitches that NG Firewall will connect to activate “promiscuous mode” click on “Properties…”
	~~[[Image:vm20.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 NG Firewall Virtual Machine connects to!
	[[Image:vm21.jpg\|none\|512px\|vCenter vSwitch Properties2]]		[[Image:vm21.jpg\|none\|512px\|vCenter vSwitch Properties2]]

Bcarmichael at 19:13, 23 January 2024

2024-01-23T19:13:49Z

Bcarmichael at 19:12, 23 January 2024

2024-01-23T19:12:14Z

← Older revision		Revision as of 19:12, 23 January 2024
Line 37:		Line 37:
	[[Image:vmware4.jpg\|none\|128px\|vCenter File->Deploy]]		[[Image:vmware4.jpg\|none\|128px\|vCenter File->Deploy]]
	* In the “Deploy OVF Template” wizard mark “Deploy from file:” And hit “Browse…”		* In the “Deploy OVF Template” wizard mark “Deploy from file:” And hit “Browse…”
	[[Image:~~vmware5~~.jpg\|none\|512px\|vCenter Deploy Wizard 1]]		[[Image:vm5.jpg\|none\|512px\|vCenter Deploy Wizard 1]]
	* Browse to the location where you saved your image and click "Open".		* Browse to the location where you saved your image and click "Open".
	* Then hit “Next”		* Then hit “Next”

Græmer: /* Download the NG Firewall Virtual Machine */

2022-11-02T18:26:19Z

Download the NG Firewall Virtual Machine

← Older revision		Revision as of 18:26, 2 November 2022
Line 28:		Line 28:
	* Download the NG Firewall Virtual Appliance:		* Download the NG Firewall Virtual Appliance:
	1. Log into your Edge Threat Management account.		1. Log into your Edge Threat Management account.
	2. Click GET ~~UNTANGLE~~ at the top right-hand corner.		2. Click GET STARTED at the top right-hand corner.
	3. Select the latest version and download the ISO file.		3. Select the latest version and download the ISO file.

Græmer at 16:00, 5 May 2022

2022-05-05T16:00:11Z

← Older revision		Revision as of 19:13, 23 January 2024
Line 40:		Line 40:
	* Browse to the location where you saved your image and click "Open".		* Browse to the location where you saved your image and click "Open".
	* Then hit “Next”		* Then hit “Next”
	[[Image:~~vmware7~~.jpg\|none\|512px\|vCenter Deploy Wizard 2]]		[[Image:vm7.jpg\|none\|512px\|vCenter Deploy Wizard 2]]
	* Read The Template Details and click “Next”.		* Read The Template Details and click “Next”.
	[[Image:~~vmware8~~.jpg\|none\|512px\|vCenter Deploy Wizard 3]]		[[Image:vm8.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”.		* 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]]		[[Image:vm9.jpg\|none\|512px\|vCenter Deploy Wizard 4]]
	* In the “Resource Pool screen” If you use Resource Pools, select the appropriate pool for the new NG Firewall VM and click "Next". Note: You can always move the VM to another Resource Pool after it's installed.		* In the “Resource Pool screen” If you use Resource Pools, select the appropriate pool for the new NG Firewall 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]]		[[Image:vm10.jpg\|none\|512px\|vCenter Deploy Wizard 5]]
	* In the “Datastore screen” Select what datastore you want use click “Next”.		* In the “Datastore screen” Select what datastore you want use click “Next”.
	[[Image:~~vmware11~~.jpg\|none\|512px\|vCenter Deploy Wizard 6]]		[[Image:vm11.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]]		[[Image:vm12.jpg\|none\|512px\|vCenter Deploy Wizard 7]]
	* Wait for the “Deploying” Progress Meter.		* Wait for the “Deploying” Progress Meter.
	[[Image:~~vmware13~~.jpg\|none\|256px\|vCenter Deploy Progress Meter]]		[[Image:vm13.jpg\|none\|256px\|vCenter Deploy Progress Meter]]
	* When it is done, Click "Close".		* When it is done, Click "Close".
	[[Image:~~vmware14~~.jpg\|none\|256px\|vCenter Deployment Completed]]		[[Image:vm14.jpg\|none\|256px\|vCenter Deployment Completed]]
	==== Verify/Configure Physical NIC to vSwitch mappings ====		==== 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 NG Firewall 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 NG Firewall 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]]		[[Image:vm20.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 NG Firewall Virtual Machine connects to!
	[[Image:~~vmware21~~.jpg\|none\|512px\|vCenter vSwitch Properties2]]		[[Image:vm21.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 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.		* 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 ====		==== Celebrate! You're at the end ====
	Now you are ready to Power on your NG Firewall VM.		Now you are ready to Power on your NG Firewall VM.

← Older revision		Revision as of 16:00, 5 May 2022
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 virtualized through a [http://en.wikipedia.org/wiki/Virtual_appliance virtual appliance] running on [http://www.vmware.com VMware] ESX or ESXi.

	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.		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 '''NG Firewall''' configuration but configuration of the virtualization hypervisor is beyond the scope of Edge Threat Management support.

	:* '''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.		:* '''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.
Line 7:		Line 7:


	== ~~Untangle~~ Support and VMware ==		== NG Firewall 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.		Arista Edge Threat Management 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 NG Firewall 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.		That being said, we'd like to make you aware that systems like NG Firewall 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 NG Firewall server is unable to process traffic. At the same time, network traffic continues to arrive. This traffic stacks up and presents itself to the NG Firewall 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).		'''In summary''': We do not recommend virtualizing NG Firewall. If you choose to install NG Firewall in a virtual environment, the support team will assist you with any issues related to the NG Firewall 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 ==		== How to install on ESX or ESXi ==
Line 26:		Line 22:

	# 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 Virtual Machine ====

	* Download the ~~Untangle~~ Virtual Appliance ~~here~~: ~~https://www~~.~~untangle~~.~~com/cmd/~~download~~/ng-firewall~~.		* Download the NG Firewall Virtual Appliance:
			1. Log into your Edge Threat Management account.
			2. Click GET UNTANGLE at the top right-hand corner.
			3. Select the latest version and download the ISO file.

	==== 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.		* Once the image is downloaded, open your VMware vSphere Client and login to your server.
	[[Image:vmware3.jpg\|none\|256px\|vCenter Login]]		[[Image:vmware3.jpg\|none\|256px\|vCenter Login]]
	* Once you are logged in, click File -> “Deploy OVF Template…”		* Once you are logged in, click File -> “Deploy OVF Template…”
Line 39:		Line 38:
	* In the “Deploy OVF Template” wizard mark “Deploy from file:” And hit “Browse…”		* In the “Deploy OVF Template” wizard mark “Deploy from file:” And hit “Browse…”
	[[Image:vmware5.jpg\|none\|512px\|vCenter Deploy Wizard 1]]		[[Image:vmware5.jpg\|none\|512px\|vCenter Deploy Wizard 1]]
	* Browse to the location where you saved your ~~OVA file~~ and click "Open".		* Browse to the location where you saved your image and click "Open".
	* Then hit “Next”		* Then hit “Next”
	[[Image:vmware7.jpg\|none\|512px\|vCenter Deploy Wizard 2]]		[[Image:vmware7.jpg\|none\|512px\|vCenter Deploy Wizard 2]]
Line 46:		Line 45:
	* In the “Name and Location screen” you may either change the name or leave it at the default. Click “Next”.		* 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]]		[[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.		* In the “Resource Pool screen” If you use Resource Pools, select the appropriate pool for the new NG Firewall 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]]		[[Image:vmware10.jpg\|none\|512px\|vCenter Deploy Wizard 5]]
	* In the “Datastore screen” Select what datastore you want use click “Next”.		* In the “Datastore screen” Select what datastore you want use click “Next”.
Line 59:		Line 58:
	* 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:vmware19.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]]		[[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 ~~Untangle~~ 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 NG Firewall Virtual Machine connects to!
	[[Image:vmware21.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:vmware15.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:vmware17.jpg\|none\|512px\|vCenter VM properties]]
Line 73:		Line 72:
	[[Image:vmware18.jpg\|none\|512px\|vCenter VM properties/tools options]]		[[Image:vmware18.jpg\|none\|512px\|vCenter VM properties/tools options]]
	==== Celebrate! You're at the end ====		==== Celebrate! You're at the end ====
	Now you are ready to Power on your ~~Untangle~~ VM.		Now you are ready to Power on your NG Firewall VM.

	== More Info and Troubleshooting ==		== More Info and Troubleshooting ==
Line 82:		Line 81:
	* [http://www.vmware.com/support/pubs/ VMware 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://www.microsoft.com/technet/prodtechnol/virtualserver/2005/proddocs/default.mspx?mfr=true Microsoft Virtual Server documentation]
	* [http://forums.untangle.com ~~Untangle~~ Community Support]		* [http://forums.untangle.com Edge Threat Management Community Support]
	* [http://www.untangle.com/live-support ~~Untangle~~ Live Support]		* [http://www.untangle.com/live-support Edge Threat Management Live Support]
	For information about using your new ~~Untangle~~ software, see our [[~~Untangle~~ Server User's Guide]].		For information about using your new NG Firewall software, see our [[NG Firewall Server User's Guide]].

	~~Happy virtual Untangling!~~