System Requirements

the following system requirements are for an esxi based deployment for litmus edge manager note esxi or a similar hypervisor is required to deploy litmus edge manager bare metal deployment is not supported 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