System Requirements
This topic provides minimum requirements for running Litmus Edge, describes the three most common configurations, and explains firewall port requirements.
Minimum Requirements
A Litmus Edge instance is designed to collect, analyze, and forward data. These data operations may require heavy computing resources to manage the day-to-day processes that a Litmus Edge instance executes. While you can run Litmus Edge on a wide range of devices, ensure that you have sufficient computing resources to avoid performance issues.
Consider the following factors when deciding on the hardware your Litmus Edge instance:
- What is the amount of data that will be processed?
- What is your hardware budget?
- How many devices will you connect to Litmus Edge?
- How many flows, analytics, applications, and integrations will you need?
- What programming language and frameworks will you use?
- Will you need frequent Litmus Edge and Litmus Edge Manager interactions (for example, automatic backups) as well?
To address some of these questions, we recommend you first install Litmus Edge on a test Virtual Machine (VM). Then, run a partial execution of all your possible workloads to see how it performs. This will provide you with a better idea whether you need less, about the same, or a multiplying factor of your test VM's computing resources. See below for setting up this VM.
Recommended Configurations
A Litmus Edge instance is typically configured for one of three deployment patterns: data pass-through, in-stream processing, or heavy in-stream processing and application usage.
Data Pass-Through
- Reading and passing data executed externally exclusively on integrations.
- Minimal data processing and storage performed on the Litmus Edge instance.
- Most computing resources consumed by only DeviceHub and data storage/forwarding to Integrations.
In-Stream Processing
- Low-volume in-stream processing of data using flows or analytics (for example, value change or anomaly detection).
- Data stored in InfluxDB for local visualization using a container running the Grafana or Python application.
- Computing resources consumed by InfluxDB, flows, analytics, containers, and DeviceHub.
Heavy In-Stream Processing and Application Usage
- High-volume in-stream processing of all collected data involving complex flows and analytics.
- Multiple flows are configured with the maximum allowed RAM.
- In analytics, many groups operate, each including multiple processors.
- Several containers may run for further data processing, traceability, downtime recording, and so on.
- InfluxDB requires additional CPU and RAM resources if a large number of devices and tags are configured.
- Each device becomes its own InfluxDB data table (measurement).
- Computing resources consumed by user-defined code within flows, applications, and analytics flows.
The following table summarizes parameters for the three starting configurations when sizing a Litmus Edge instance.
| Data pass-through | In-stream processing | Heavy in-stream processing and application usage |
|---|---|---|---|
Devices | 1-5 | 5-10 | 10+ |
Average Tags per Device | 10-20 | 20-100 | 100+ |
Flows Instances | 0-4 | 1-4 | 1-4 |
Average Flow Nodes | < 10 | 10-50 | 50+ |
Analytics | 0-5 | 5-25 | 25+ |
Applications/ Containers | 0 | 1-2 | 2+ |
Integrations | 1-2 | 1-5 | 5+ |
InfluxDB Usage | Optional | Mandatory | Mandatory |
Cores | 4 | 8 | 12+ |
Memory(RAM) | 8-16 GB | 16-32 GB | 32+ GB |
Storage (Disc) | 100-250 GB | 250- 500 GB | 500+ GB |
NIC (Network Interface) | Typically at least two:
| Typically at least two:
| Typically at least two:
|
Firewall Port Configuration Requirements
Note: You can also managing port in Litmus Edge. See Manage Firewall Rules to learn more.
The firewall managing Litmus Edge's traffic must always open the following port to allow you to access the Web User Interface.
Function for Litmus Edge | Port # | Encrypted | Direction | Protocol | Description | Source (Port is used by who/what) | Destination (Port must be opened at) |
|---|---|---|---|---|---|---|---|
Access Litmus Edge through a Web User Interface | 443 | Yes SSL | Inbound | TCP | HTTPS | Litmus Edge Users | Litmus Edge |
To allow a connection between Litmus Edge and Litmus Edge Manager, the following ports must be open.
Function for Litmus Edge | Port # | Encrypted | Direction | Protocol | Description | Source (Port is used by who/what) | Destination (Port must be opened at) |
|---|---|---|---|---|---|---|---|
Redirects 443 | 80 | No | Inbound | TCP | HTTP | Litmus Edge Users | Litmus Edge |
Connect Litmus Edge to Litmus Edge Manager | 8883 | Yes MQTTS | Outbound | TCP | MQTT-SSL | Litmus Edge | Litmus Edge Manager and Customer MQTT Broker |
Connect Litmus Edge to Litmus Edge Manager | 443 | Yes | Outbound | TCP | HTTPS | Litmus Edge | Litmus Edge Manager |
Connect Litmus Edge to Litmus Edge Manager | 51820 | Yes | Outbound | UDP | UDP Litmus Edge Manager Remote Access | Litmus Edge | Litmus Edge Manager |
The firewall managing Litmus Edge's traffic must open Only if corresponding services are present and running.
Function for Litmus Edge | Port # | Encrypted | Direction | Protocol | Description | Source (Port is used by who/what) | Destination (Port must be opened at) |
|---|---|---|---|---|---|---|---|
Use Litmus Edge as an FTP Server | 21, 2121 | No | Inbound | TCP | FTP | Customer FTP Server | Litmus Edge |
Use Litmus Edge as an SSH Server. Used for backend support access | 22 | Yes Session key | Inbound | TCP | SSH | Litmus Support Team | Litmus Edge |
Use Litmus Edge as an LDAP Client | 389 | No | Outbound | TCP | LDAP | Litmus Edge | Customer LDAP Server |
Use Litmus Edge as an LDAP Client | 636 | Yes SSL | Outbound | TCP | LDAP with SSL | Litmus Edge | Customer LDAP Server |
Use Litmus Edge as an OPC UA Server | 4840 | Yes (Depends on server settings) | Inbound | TCP/UDP | OPC UA Server | Customer Northbound Application | Litmus Edge |
Collaboration with name servers to replace IP of Litmus Edge with a name server | 5353 | No | Outbound | UDP | mDNS (Multicast DNS) | Litmus Edge | Multicast Local Network |
Collaboration with name servers to replace IP of Litmus Edge with a name server | 5355 | No | Inbound | TCP/UDP | LLMNR (Link-Local Multicast Resolution) | 224.0.0.252 | Litmus Edge |
Remote access over internet when accessing Litmus Edge | 9993 | Yes (asymmetric public key encryption) | Outbound | UDP | Remote Access | Litmus Support Team | Litmus Edge |
PLC-Specific Ports
The firewall managing Litmus Edge's traffic must open specific ports for certain PLC devices to connect to Litmus Edge. To manage firewall rules in Litmus Edge, see Manage Firewall Rules.
Ports for Industrial Systems and Sensors Connections are PLC specific and should be open on a case-by-case basis. See the Industrial Systems Connection Guide for more information.
Marketplace Ports
Marketplace applications manage their own ports. Those ports are application-specific and are outside of the iptables firewall.
Other Ports
Any other ports are blocked by the iptables firewall. This means that the Litmus Edge flows application can initiate only outgoing traffic and cannot listen to incoming connections.
Supported Browsers
Litmus Edge 4.0.4 and 4.0.8 support the following browsers.
Browser | Version | Release date |
|---|---|---|
Chrome | 107 | 2022-10-27 |
Edge | 107 | 2022-10-27 |
Firefox | 104 | 2022-08-23 |
Safari | 16 | 2022-09-12 |