---
title: System Requirements
slug: edgemanager/quickstart-guide/system-requirements
description: Review the system requirements for an ESXi-based deployment for Litmus Edge Manager.
docTags:
createdAt: 2022-03-30T21:31:38.000Z
---
The following system requirements are for an ESXi-based deployment for Litmus Edge Manager.
:::hint{type="info"}
**Note**: ESXi or a similar hypervisor is required to deploy Litmus Edge Manager. Bare metal deployment is not supported.
:::
:::hint{type="warning"}
**Important**: Depending on system resources, first time installation setup may take up to 30 minutes to complete.
:::
# Minimum Requirements
Review the following minimum requirements for desktop distribution.
| **Hardware** | **Minimum Requirements** |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Processor | - Intel x86 64-bit processor
- 16 Core\@2.2Ghz (Example: Intel i5) |
| Memory | 16 GB RAM |
| Storage | 80 GB available space |
| Network ports | 1 Bridged
Direct connection to corporate LAN allows for internet connection and other TCP/IP communication to other systems. An available IP is required. |
| Firmware | EFI |
| Storage Controller Type | SATA |
# Recommended Configurations
Review the following recommended configurations for data center distribution.
| **Hardware** | **Recommended Configuration** |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Processor | - Intel x86 64-bit processor
- 32 Core\@2.2Ghz (Example: Intel Xeon) |
| Memory | 32 GB RAM |
| Storage | 1 TB available space or more |
| Network ports | 1 Bridged
Direct connection to corporate LAN allows for internet connection and other TCP/IP communication to other systems. An IP address must be acquired to this. |
| Firmware | EFI |
| Storage Controller type | SATA |
# Firewall Port Configuration Requirements
The Litmus Edge Manager must have the following ports open for the following corresponding functions.
| **Port** | **Protocol** | **Encrypted** | **Optional** | **Direction** | **Port Function / Usage for Litmus Edge Manager** | **Description / Additional Details** | **Source**
**(Port is used by who/what)** | **Destination**
**(Port must be opened at)** |
| -------- | ------------ | ------------------------------------------------ | ------------ | ------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------- |
| 22 | TCP | Yes
Session Key | Yes | Inbound | SSH | Managing a Litmus Edge
Managing instances using SSH | Litmus Edge Manager
Admins | Litmus Edge Manager |
| 80 | TCP | Redirects to HTTPS | Yes | Inbound | HTTP, redirect SSL | Accessing Litmus Edge Manager UI if you entered only the domain name without the protocol in a browser
Domain validation when using Let's Encrypt SSL | Litmus Edge Manager
users | Litmus Edge Manager |
| 123 | UDP | No | Yes | Inbound | Network Time Protocol | Used to transform Litmus Edge Manager version 2.8.0 and later as an NTP Server. See [NTP](docId\:hRmAskLSu9CAdrlP7k-UE) for details. | Litmus Edge | Litmus Edge Manager |
| 443 | TCP / HTTPS | Yes
SSL | No | Inbound | Access to Litmus Edge Manager UI | Access to Litmus Edge Manager REST API
Access to Litmus Edge Manager Admin Docker registry
Access to Keycloak authorization server
Used by Litmus Edge Manager to communicate with Litmus Edge
Pre-signed links are generated on this port.
Minio Storage
(Update file repo) | Litmus Edge
Litmus Edge Manager
users | Litmus Edge Manager |
| 8123 | TCP | No
optional (settable on screen) | Yes | Inbound | Litmus Edge Manager
Clickhouse database HTTP interface | | Third-party Integration / Reporting tools | Litmus Edge Manager |
| 8446 | TCP | Yes
SSL | No | Inbound | Access to Litmus Edge Manager Admin UI | | Litmus Edge Manager
Admins | Litmus Edge Manager |
| 8543 | TCP | Yes
SSL | Yes | Inbound | Litmus Edge Manager
Clickhouse database HTTPS interface | | Third-party Integration / Reporting tools | Litmus Edge Manager |
| 8883 | MQTT / TCP | Yes
MQTTS | No | Inbound | Litmus Edge Manager MQTT server | CC Connector: Sending data from Litmus Edge to Litmus Edge Manager | Litmus Edge | Litmus Edge Manager |
| 9000 | TCP | Optional (encryption initiated from client side) | Yes | Inbound | Litmus Edge Manager
Clickhouse Native interface | | Third-party Integration / Report tools | Litmus Edge Manager |
| 9004 | TCP | Optional (encryption initiated from client side) | Yes | Inbound | Litmus Edge Manager
Clickhouse MySQL interface | | Third-party Integration / Reporting tools | Litmus Edge Manager |
| 9092 | TCP | Optional (encryption initiated from client side) | Yes | Inbound | Access to Litmus Edge Manager
Kafka PLAIN connection | | Third-party Integration / Reporting tools | Litmus Edge Manager |
| 9093 | TCP | Yes
SSL (Optional) | Yes | Inbound | Access to Litmus Edge Manager Kafka SSL connection | | Third-party Integration / Reporting tools | Litmus Edge Manager |
| 51820 | UDP | Yes
Remote Access | No | Inbound | EdgeRemote
(uses Remote Access) | Enables Litmus Edge Manager management (Remote UI, templates, marketplace, metrics and so on) of all connected Litmus Edge instances.
Used for remotely updating the version of connected Litmus Edge instances.
Requires 443 to be open. | Litmus Edge | Litmus Edge Manager |