FileConnect Enterprise v3 (FCEv3) operates as a virtual machine (VM) deployed on supported hypervisors. This document outlines the hardware, software, and network requirements necessary to successfully install and operate the FCEv3 virtual appliance.
1. Hardware Hosting the Virtual Machine
FCEv3 runs within a virtual machine hosted on a compatible hypervisor. The host machine must provide adequate resources to support both the hypervisor and the virtual machine workloads.
Minimum Host Requirements
| Component | Requirement |
|---|---|
| Processor (CPU) | x86-compatible processor with virtualization support (Intel VT-x or AMD-V) |
| Memory (RAM) | Minimum 32 GB (additional memory recommended for larger datasets) |
| Storage | Minimum 200 GB per TB of managed data (SSD recommended) |
| Network Interface | 1 Gbps or faster Ethernet interface |
2. Supported Operating Systems (Host OS)
The following operating systems are supported for hosting the hypervisor and FCEv3 virtual machine.
Red Hat Enterprise Linux (RHEL)
Supported Versions: 8 and 9
Must be a vendor-supported release of RHEL.
Ubuntu Server
Supported Versions: 24.04, 22.04, and 20.04
Must follow Ubuntu’s active support matrix.
Microsoft Windows Server
Supported versions under Microsoft’s current support policy.
-
Windows 11 is supported for development and demonstration purposes only.
3. Hypervisor Requirements
The hypervisor is responsible for running the FCEv3 virtual machine on the host OS.
Supported Hypervisors
VMware
Any VMware product capable of running x86-based virtual machines.
-
Examples:
VMware Workstation Pro
VMware ESXi
VMware vSphere
For installation and configuration details, refer to Broadcom’s official documentation: VMware by Broadcom – Cloud Computing for the Enterprise.
Oracle VirtualBox
Fully supported for FCEv3.
-
For installation and configuration details, see Oracle’s official documentation: VirtualBox Official Documentation.
4. Virtual Machine (Guest) Specifications
The FileConnect Enterprise v3 virtual machine is built on CentOS Stream 9 (x86 architecture).
Minimum Configuration
| Component | Requirement |
|---|---|
| vCPU | 4 |
| Memory | 32 GB |
| Disk Space | >200 GB per TB of managed data |
| Operating System | CentOS Stream 9 |
5. Network Requirements
The FCE virtual machine must be connected to all file shares and volumes it is intended to manage.
Required Network Access
The FCE virtual machine must have access to all relevant storage systems, file shares, and volumes.
Port Access
The following ports must be accessible for users and services outside of the VM:
| Port | Service | Description |
|---|---|---|
| 8000 | Diskover | Data indexing and analytics |
| 8080 | FCE Management UI | Web-based management interface |
| 9090 | FCE API | API access for integrations |
| 5601 | Kibana | Dashboard and reporting interface (if enabled) |
Note: For more detailed network and security configuration, refer to Security Hardening FCEv3 | Network Requirements.
6. External Site Access
The FCE virtual machine requires external network access to several services for licensing, telemetry, and integration.
Required External Endpoints
| Service | Endpoint |
|---|---|
| Records365 Connector (Regional) | e.g., connector-usw.records365.com (for U.S. region) |
| LaunchDarkly (Feature Flags) |
app.launchdarkly.com, stream.launchdarkly.com, sdk.launchdarkly.com
|
| Microsoft Application Insights |
dc.applicationinsights.azure.com, dc.applicationinsights.microsoft.com, dc.services.visualstudio.com
|
| Microsoft Authentication | login.microsoftonline.com |
| Binary Submissions | *.windows.net |