Scope
This article applies for installing a Peplink Fusionhub Server on Vmware Esxi.
This article applies only for Vmware ESXi version using the depreciated vsphere Windows Thick Client.
For newer versions of Vmware vSphere refer to corresponding article: How To Install a Fusionhub Server on latest Vmware ESXI versions.
https://help.venntelecom.com/a/solutions/articles/44001551246?lang=en
Intended Audience
This article is intended for IT Managers, IT staff and Project Managers.
In This Task
- Summary
- Solution
1. Minimum Specfications
2. Download last version of OVF Template
3. Install Fusionhub Server from OVF Template
4. Network Configuration
5. Power Up the Fusionhub Server
6. Fusionhub Interface configuration
7. licencing
- Related articles
- Troubleshooting
Summary
Install a Fusionhub Server from a OVF file on recent Vmware ESX using Vsphere Windows Thick Client.
Solution
1. Minimum specifications.
- Processor Intel Core i5 - 1 GB RAM - 400 MB Disk
- In order to deploy the OVF template successfully, please make sure that your ESXi server supports virtual machine version 8, which runs on VMware ESXi 5.5 and later.
- 1 Public IP is needed for setting up the Pepvpn tunnels from the routers to the Fusionhub Server.
2. Download last version of OVF template.
https://www.peplink.com/products/fusionhub
Unzip the file to a directory accessible by the Vmware Server.
3. Install Fusionhub Server from OVF Template.
After successffully logged into the Vmware Server:
Choose the Vmware Server you want the Fusionhub to be installed and connect to it with Vsphere Windows thick client.
Click File in the Menu Bar
Choose Deploy OVF Template... to deploy the FusionHub OVF template downloaded.
On the Source dialog of the Deploy OVF Template wizard, click Browse. Locate the FusionHub.ova template file on your computer and click Next.
On the Name and Location dialog, type a name or keep the default setting. Click Next.
Keep the default settings on the Disk Format dialog. Click Next.
On the Ready to Complete dialog, review the deployment settings. Click Finish to complete the process and close the wizard.
Once you have completed the steps above, a FusionHub virtual machine is created.
Fusionhub is now ready to be configured, don't start it yet.
4. Network configuration.
The Fusionhub Networking can be configured in multiple ways.
A. Fusionhub directly published on the Internet with no access to the local LAN/DMZ : then there is only one Network Interface in the Fusionhub Server and the WAN IP in the Fusionhub Server (called WAN_IP) is the Public IP (called PUBLIC_IP).
B. Fusionhub directly published on the Internet with access to the LAN/DMZ : then 2 Network interfaces are configured in the Fusionhub Server, One (Called WAN_IP) with the Public IP (Called PUBLIC_IP) and one with a LAN/DMZ/ IP (Called DMZ_IP). In that case the Internal Firewall of the Fusionhub Server has to be used to limit and protect the traffic.
C. Fusionhub behind an existing firewall with only 1 Network Interface in the Fusionhub Server : then WAN IP of the Fusionhub Server (Called WAN_IP) is a LAN/DMZ IP (Called DMZ_IP) on the LAN/DMZ subnet of the Firewall, wich will be Natted to the Public IP (Called PUBLIC_IP) published by the Firewall. The Fusionhub Server will also have access to the internal LAN/DMZ subnet on the same interface.
D. Fusionhub behind a Firewall with 2 network interfaces in the Fusionhub Server : then WAN IP of the Fusionhub Server (Called WAN_IP) is a LAN/DMZ IP (Called DMZ_IP) on the LAN/DMZ subnet of the Firewall, wich will be Natted to the Public IP (Called PUBLIC_IP) published by the Firewall. The second Interface of the Fusionhub Server will then be configured with an IP (Called LAN_IP) on the subnet of the local LAN (or DMZ eventually).
Depending on your Network configuration the right option has to be choosen.
If configuring the Fusionhub Server behind a Firewall consider reading the related article found at the bottom in the "Related Articles" section.
Note: FusionHub virtual machines support a maximum number of two network adapters.
By default, Network adapter 1 is set as the WAN port, and Network adapter 2 is set as the LAN port.
Click FusionHub in the column on the left side of the dialog to select the virtual machine.
Click Edit virtual machine settings to begin adding an Ethernet adapter to the FusionHub virtual machine.
Click Add, found under the Hardware tab on the FusionHub – Virtual Machine Properties dialog.
On the Add Hardware dialog, select Ethernet Adapter. Click Next.
On the Network Type dialog, select VMXNET 3 as the Adapter Type.
Select the appropriate network and port settings from the drop-down menus under Network Connection.
Check Connect at power on to connect the NIC when the virtual machine is powered on.
Click Next.
On the Ready to Complete dialog, review your settings and click Finish.
Click OK to finish adding hardware.
Reminder: FusionHub virtual machines support a maximum number of two network adapters.
By default, Network adapter 1 is set as the WAN port, and Network adapter 2 is set as the LAN port.
5. Power up the Fusionhub Server
Click Power on the virtual machine to run FusionHub.
When the FusionHub virtual machine is powered on, right-click FusionHub.
Select Open Console for general information about FusionHub, including:
Open Console for general information about FusionHub, including:
● FusionHub version
● System information
● Network settings:
Method: DHCP
IP Address: None
Admin: http://169.254.254.254
The default WAN connection method is DHCP. If the DHCP server is available on your network, the FusionHub IP address will be automatically obtained by the DHCP server.
In this case, the console will look similar to the following:
6. Fusionhub Interface Configuration.
1. To access FusionHub’s Web admin interface, connect your computer to the network on which FusionHub is running.
2. Enter the Web admin address (i.e., http://192.168.95.14) in your Web browser's address field.
3. Next, access the Web admin interface by entering admin for both the user name and password. The default is admin and admin
4. Once you have successfully logged in, the Setup Wizard will be displayed.
FusionHub’s Setup Wizard leads you step-by-step through the process of configuring your WAN connection.
Click Next to begin.
Select the WAN connection method from the following screen. The default selection is DHCP.
Depending on the selected connection type, further configuration may be needed:
• If Static is selected, the Setup Wizard will display Static IP Settings
• If DHCP is selected, the Setup Wizard will display DHCP Settings.
• If PPPoE is selected, the Setup Wizard will display PPPoE Settings.
During this step, make sure the FusionHub and ESXi servers are on the same network if Static is selected. For example:
If the ESXi server’s IP settings are:
IP address: 10.8.9.124
Subnet mask: 255.255.0.0
Default gateway: 10.8.8.1
Configure port settings as follows:
IP address: 10.8.x.x (x denotes any integer from 2 to 254)
Subnet mask: 255.255.0.0
Default gateway: 10.8.8.1
If there is more than one port on the ESXi server and you have assigned two network adapters to this FusionHub virtual machine, the LAN port configuration dialog will be open. The default selection is Static.
● If Static is selected, the Setup Wizard will display Static IP Settings
● If DHCP is selected, the Setup Wizard will display DHCP Settings.
● If Disable is selected, the Setup Wizard will move to the next step.
Click Next to define a Local ID before using PepVPN. The local ID is a text string that identifies this local unit when establishing a VPN connection.
You can give this field any name you want (ie. temp), it will later on be defined by Inconcontrol Central Management.
Click Next to choose the time zone of your country/region.
Check Show all to display all time zone options and chose one in the drop list according to your location.
Then click Next.
Check to make sure all settings have been configured correctly, and then click Save and Apply Settings.
At this point contact Venn on [email protected] or +32 2 318 48 25 to obtain a licence.
7. Licencing.
When the license is successfully activated, you will see the following screen:
When Licence has been successfully activated the Fusionhub Server is assigned with a serial number.
The information shown on the FusionHub console will change to the following:
In Vmware Console this is visible:
Serial number of installed Fusionhub Server has to be communicated to Venn in order to add it to the Incontroll Central Management portal.
Important Note:
After having confirmed the licence the Fusionhub Server will no more be available on http but only on https://WAN_IP:5312 (an
The default password will also automaticaly be changed for Security reasons.
Please contact [email protected] or +32 2 318 48 25 to finalyse installation.
Related Articles
https://help.venntelecom.com/a/solutions/articles/44001551246?lang=en
https://help.venntelecom.com/a/solutions/articles/44000984120?lang=en
Troubleshooting
For troubleshooting please contact our support on [email protected] or +32 2 318 48 25
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article