To deploy Tunnel with Unified Access Gateway, ensure that your system meets the following requirements:
Hypervisor Requirements
Unified Access Gateway that deploys the Tunnel requires a hypervisor to deploy the virtual appliance. You must have a dedicated admin account with full privileges to deploy the OVF.
Supported Hypervisors
- VMware vSphere web client
- Microsoft Hyper-V on Windows Server 2012 R2 or Windows Server 2016
Software Requirements
Ensure that you have the most recent version of Unified Access Gateway. Tunnel supports backwards compatibility between Unified Access Gateway and the Workspace ONE UEM console. The backward compatibility allows you to upgrade your Tunnel server shortly after upgrading your Workspace ONE UEM console. To ensure parity between Workspace ONE UEM console and Tunnel, consider planning an early upgrade.
Hardware Requirements
The OVF package for Unified Access Gateway automatically selects the virtual machine configuration that Tunnel requires. Although you can change these settings, do not change the CPU, memory, or disk space to smaller values than the default OVF settings.
To change the default settings, power off the VM in vCenter. Right-click the VM and select Edit Settings.
The default configuration uses 4 GB of RAM and 2 CPUs. You must change the default configuration to meet your hardware requirements. To handle all the device loads and maintenance requirements, consider running a minimum of two Tunnel servers.
Hardware Requirements
| Number of Devices | Up to 40000 | 40000-80000 | 80000-120000 | 120000-160000 |
|---|---|---|---|---|
| Number of Servers | 2 | 3 | 4 | 5 |
| CPU Cores | 4 CPU Cores* | 4 CPU Cores each | 4 CPU Cores each | 4 CPU Cores each |
| RAM (GB) | 8 | 8 | 8 | 8 |
| Hard Disk Space (GB) | 10 GB for distro (Linux only) 400 MB for installer ~10 GB for log file space** | |||
| *It is possible to deploy only a single Tunnel appliance as part of a smaller deployment. However, consider deploying at least two load-balanced servers with four CPU Cores each regardless of the number of devices for uptime and performance purposes. **10 GB for a typical deployment. Scale the log file size based on your log use and requirements for storing the logs. |
Was this page helpful?