Find the minimum and recommended system requirements for Private Access Connector virtual appliance deployment.
System Requirements
-
CPU Architecture: x86-64-v2 or later
-
Virtual CPUs: 2 cores minimum, 4 cores recommended
-
Memory: 4 GB minimum, 8 GB recommended
-
Disk: 50 GB
Supported Platforms
| Platform | Version | Virtual Network Adapter |
|
VMware ESXi
|
7.0 U1 or later. 8.0 or later
|
VMXNET3 with a minimum speed of 1,000 MB/s
|
|
Microsoft Azure
|
-
|
N/A
|
|
Amazon Web Services
|
-
|
N/A
|
|
Google Cloud Platform
|
-
|
N/A
|
|
Microsoft Hyper-V
|
2016 and later
|
N/A
|
|
Nutanix AHV
|
-
|
VirtIO with a minimum speed of 1,000 MB/s
|
VMware EVC Compatibility
If you deploy connectors on VMware vSphere with Enhanced vMotion Compatibility (EVC) enabled, the EVC baseline must expose x86-64-v2 instructions to guest VMs.
Minimum EVC levels for x86-64-v2 compatibility
|
Vendor
|
Minimum EVC baseline
|
|
Intel
|
Nehalem
|
|
AMD
|
Barcelona or later
|
If your cluster EVC level is set below these baselines, guest VMs will not have access
to the required instruction sets and the connector will fail to boot. Consult your
VMware administrator to verify or raise the EVC level before deploying.
ImportantChanging the EVC level on an existing cluster may require all VMs to be powered off.
|
Sizing
TrendAI™ advises against allowing the host to dynamically configure VM resources as is the
default in VMware. Instead, configure the VM to reserve at least the number of vCPUs
and memory listed in the system requirements.
TrendAI™ suggests deploying more private access connectors with lower specifications rather
than fewer connectors with higher specifications. This approach enhances horizontal
scalability. For instance, if you have fewer higher-specification connectors and one
fails, it could disrupt a large amount of user application traffic or sessions. The
failure of a lower specification but more numerous connector would have a lesser impact.
Throughput with recommended configuration example
Below is an example throughput measured with the following setup:
-
Amazon AWS VM with recommended configuration of 4 vCPUs and 8 GB RAM
-
Use: Private application access
-
Average TCP round trip time: 85 msec
-
No double encryption for http traffic
Note that the actual throughput may vary depending on factors such as the number of
concurrent users, your internal network configuration, and latency. Ensure that you
have sufficient private access connectors to support the connection and provide room
for failover (N+1). To boost overall throughput, add more connectors to the same connector
group as needed for your deployment.
Concurrent users vs. throughput (Mbps)
|
Concurrent users using the secure access module
|
Total throughput of private access connector (Mbps)
|
|
1016
|
508
|
|
600
|
600
|
|
315
|
630
|
|
115
|
575
|
