System Requirements
System Requirements ensure optimal performance and reliability for your ServiceOps deployment by providing clear hardware, software, and network specifications for different deployment scenarios.
This document outlines the comprehensive system requirements for deploying ServiceOps on-premises. Understanding these requirements is crucial for IT administrators and implementation consultants to plan and execute successful deployments that meet your organization's performance and scalability needs.
Pre-Deployment Checklist
Before you begin, ensure you have the following ready:
- Servers: Correct number of servers provisioned for your chosen deployment model (e.g., 1 for Standalone, 3 for HA).
- Operating System: A supported OS (like Ubuntu 22.04 LTS) installed and updated on all servers.
- Static IP Addresses: Assigned to all servers.
- Firewall Ports: Key ports (e.g., 22, 80, 443, 5432) opened as per the requirements table.
- Sudo User: A non-root user with
sudoprivileges available. - Internet Access: Required on servers for downloading packages and activation.
Common System Requirements
The following requirements are applicable to all deployment models (Standalone, Distributed, HA, and DR). Deployment-specific requirements are detailed in the tabs below.
Software Requirements
Operating System and Software Dependencies
Server Operating Systems
| Operating System | Version | Architecture | Support Level | Notes |
|---|---|---|---|---|
| Ubuntu | 22.04.1 LTS | x86_64 | Full Support | Recommended for new deployments |
| Ubuntu | 24 LTS | x86_64 | Full Support | Latest LTS version |
| Red Hat Enterprise Linux | 9.2 | x86_64 | Full Support | Latest RHEL version |
| Red Hat Enterprise Linux | 9.4 | x86_64 | Full Support | Latest RHEL version |
| Pardus OS | Latest | x86_64 | Limited Support | Community distribution |
Client Operating Systems
| Operating System | Version | Architecture | Support Level | Notes |
|---|---|---|---|---|
| Windows Server | 2016 and above | x86_64 | Full Support | Enterprise server environments |
| Windows 10 | Enterprise and above | x86_64 | Full Support | Desktop client environments |
| Windows 11 | Enterprise and above | x86_64 | Full Support | Latest Windows client OS |
| Ubuntu | 22.04 LTS | x86_64 | Full Support | Linux desktop environments |
| Ubuntu | 24.04 LTS | x86_64 | Full Support | Latest Ubuntu LTS version |
Required Packages
Before installation, ensure the following package is installed:
apt install msitools
Database Requirements
- PostgreSQL: Included with ServiceOps installation
- Database Storage: Separate storage recommended for production deployments
Network Requirements
Port Requirements
Port Requirements
ServiceOps requires the following ports to be open for general operation. Additional port requirements for specific deployment models are noted in their respective tabs.
| Category | Service | Source | Destination | Ports | Description |
|---|---|---|---|---|---|
| Web Access & Communication | HTTP/HTTPS | ServiceOps Server | End Users | 80 / 443 | End-user access to ServiceOps web interface |
| Main Server, Analytics Server | ServiceOps Server | Analytics Server | 8080–8082 | Main Server ↔ Analytics Server communication | |
| Plugin Server | ServiceOps Server | Plugin Server | 5050 | Plugin Server communication | |
| Database | PostgreSQL | App Server | DB Server | 5432 | PostgreSQL database communication |
| Remote Access & Management | SSH | ServiceOps Server | Linux Environment | 22 | Used for Secure Shell (SSH) remote access to servers for administration and management purposes. |
| WMI | ServiceOps Server | Windows Devices | 135, 445, 5000–6000 (TCP), 49152–65535 | Windows Management Instrumentation (WMI) ports used for remote management and monitoring in Windows environments. These are dynamic ports used by WMI. | |
| Mesh RDP (External) | ServiceOps Server | End Users | 8443 | Mesh RDP Server (remote access for client machines) | |
| Mesh RDP (Internal) | Internal | Internal | 4430 | Internal Mesh RDP Server communication | |
| Email Communication | SMTP | ServiceOps Server | Email Servers | 25 / 465 / 587 | Simple Mail Transfer Protocol (SMTP) port used for sending email. |
| POP3 | ServiceOps Server | Email Servers | 110 / 995 | Post Office Protocol version 3 (POP3) ports for retrieving email. | |
| IMAP | ServiceOps Server | Email Servers | 143 / 993 | Internet Message Access Protocol (IMAP) ports for accessing email. | |
| Authentication & Directory Services | LDAP | ServiceOps Server | AD Server | 389 | Lightweight Directory Access Protocol (LDAP) port for accessing directory services. |
| LDAPS | ServiceOps Server | AD Server | 636 | These connections allow users to access network devices as well as organizational data. | |
| Network & Monitoring | DNS | ServiceOps Server | Firewall/Router | 53 | Used for Domain Name System (DNS) resolution to translate domain names to IP addresses. |
| SNMP | ServiceOps Server | SNMP Devices | 161 | Simple Network Management Protocol (SNMP) port used for logging and management information with remote monitoring applications. | |
| ARP | ServiceOps Server | Firewall/Router | 219 | Address Resolution Protocol (ARP) port for mapping IP addresses to MAC addresses. | |
| TCP (General) | ServiceOps Server | LAN Network | Random TCP ports | General Transmission Control Protocol (TCP) ports for various applications. |
Connectivity and Security
- Internet Connectivity: Required for software updates, license activation, cloud features, and email notifications.
- Firewall Configuration: Ensure required ports are open.
- Antivirus Exclusions: Whitelist ServiceOps executables and folders.
- Network Segmentation: Consider DMZ deployment for enhanced security.
Additional Requirements
Storage, Virtualization, and Maintenance
- SSD Storage: Recommended for database and application servers.
- Backup Storage: Plan for 2-3x current data size for backups.
- Log Storage: Allocate additional space for system logs and audit trails.
- Virtualization Support: Compatible with VMware vSphere, Microsoft Hyper-V, KVM, and other platforms.
- Monitoring and Maintenance: Implement system monitoring, log management, and a regular backup strategy.
Deployment-Specific Requirements
Select the tab corresponding to your intended deployment model to view the specific requirements.
- Standalone
- Distributed
- Multi-Site
- High Availability (HA)
- Disaster Recovery (DR)
A Standalone deployment runs all ServiceOps components on a single server.
Hardware Requirements
Service Desk Requirements
| Concurrent Technicians | CPU | RAM | Storage |
|---|---|---|---|
| 1-5 | 4 Core | 8 GB | 200 GB |
| 5-20 | 8 Core | 16 GB | 500 GB |
| 20-50 | 16 Core | 32 GB | 1 TB |
| 50-100 | 32 Core | 64 GB | 1 TB |
Asset Management Requirements
| Asset Count | CPU | RAM | Storage |
|---|---|---|---|
| 1-1000 | 4 Core | 8 GB | 200 GB |
| 1000-5000 | 8 Core | 16 GB | 500 GB |
| 5000-10000 | 16 Core | 32 GB | 1 TB |
| 10000-25000 | 32 Core | 64 GB | 1 TB |
Combined Service Desk and Asset Management
| Concurrent Technicians | Asset Count | CPU | RAM | Storage |
|---|---|---|---|---|
| 1-5 | 1-1000 | 8 Core | 12 GB | 500 GB |
| 5-20 | 1000-5000 | 12 Core | 24 GB | 500 GB |
| 20-50 | 5000-10000 | 24 Core | 48 GB | 1 TB |
| 50-100 | 10000-25000 | 48 Core | 96 GB | 1 TB |
Patch Management Requirements
| Endpoint Count | CPU | RAM | Storage |
|---|---|---|---|
| 1-1000 | 8 Core | 16 GB | 300 GB |
| 1000-5000 | 16 Core | 32 GB | 500 GB |
| 5000-10000 | 32 Core | 64 GB | 500 GB |
File/Relay Server for Patch Management
Note: One file server is required per location
| Endpoint Count | CPU | RAM | Storage |
|---|---|---|---|
| 1-1000 | 4 Core | 8 GB | 500 GB |
| 1000-5000 | 4 Core | 8 GB | 1 TB |
| 5000-10000 | 8 Core | 16 GB | 1 TB |
Bandwidth Requirements
| Concurrent Users | Minimum Bandwidth |
|---|---|
| 1-10 | 50 Mbps |
| 10-50 | 100 Mbps |
A Distributed deployment separates the Application and Database components onto different servers.
Hardware Requirements
Service Desk - Distributed Architecture
| Concurrent Technicians Login | Deployment Component | Hardware Instances | vCPU | RAM | Storage | Bandwidth |
|---|---|---|---|---|---|---|
| 1-10 | APP | 1 | 4 Core | 8 GB | 200 GB | 50 Mbps |
| DB | 1 | 4 Core | 8 GB | 200 GB | ||
| 10-20 | APP | 1 | 8 Core | 16 GB | 200 GB | 50 Mbps |
| DB | 1 | 4 Core | 8 GB | 200 GB | ||
| 20-50 | APP | 1 | 16 Core | 32 GB | 200 GB | 100 Mbps |
| DB | 1 | 8 Core | 16 GB | 500 GB | ||
| 50-100 | APP | 1 | 16 Core | 32 GB | 500 GB | 100 Mbps |
| DB | 1 | 16 Core | 32 GB | 500 GB | ||
| 100-200 | APP | 1 | 32 Core | 64 GB | 500 GB | 100 Mbps |
| DB | 1 | 16 Core | 32 GB | 500 GB |
Asset Management - Distributed Architecture
| Asset Count | Deployment Component | Hardware Instances | vCPU | RAM | Storage | Bandwidth |
|---|---|---|---|---|---|---|
| 1-1000 | APP | 1 | 4 Core | 8 GB | 200 GB | 100 Mbps |
| DB | 1 | 4 Core | 8 GB | 200 GB | ||
| 1000-5000 | APP | 1 | 8 Core | 16 GB | 200 GB | 100 Mbps |
| DB | 1 | 8 Core | 16 GB | 500 GB | ||
| 5000-10000 | APP | 1 | 16 Core | 32 GB | 500 GB | 100 Mbps |
| DB | 1 | 16 Core | 16 GB | 1 TB | ||
| 10000-25000 | APP | 1 | 32 Core | 64 GB | 500 GB | 100 Mbps |
| DB | 1 | 32 Core | 64 GB | 1 TB |
Patch Management - Distributed Architecture
| Endpoint Count | Deployment Component | Hardware Instances | vCPU | RAM | Storage/HardDisk | Bandwidth |
|---|---|---|---|---|---|---|
| 1-1000 | APP | 1 | 8 Core | 16 GB | 200 GB | 100 Mbps |
| DB | 1 | 4 Core | 8 GB | 200 GB | ||
| Relay Server | 1 | 4 Core | 8 GB | 500 GB | ||
| 1000-5000 | APP | 1 | 16 Core | 32 GB | 500 GB | 100 Mbps |
| DB | 1 | 8 Core | 16 GB | 500 GB | ||
| Relay Server | 5 | 4 Core | 8 GB | 500 GB | ||
| 5000-10000 | APP | 1 | 16 Core | 32 GB | 500 GB | 100 Mbps |
| DB | 1 | 16 Core | 32 GB | 1 TB | ||
| Relay Server | 10 | 4 Core | 8 GB | 500 GB |
Network Requirements
- Static IP Addresses: Both application and database servers must have static IP addresses.
A high-speed, low-latency network connection between the Application and Database servers is required (recommended: < 10ms latency). Higher latency will severely degrade application performance.
Bandwidth Requirements
| Concurrent Users | Minimum Bandwidth |
|---|---|
| 1-10 | 50 Mbps |
| 10-200 | 100 Mbps |
Server Requirements
- Operating System: Ubuntu 22.04 LTS or RHEL/CentOS 8+
- Database Server: Clean PostgreSQL installation (remove existing PostgreSQL if present)
A Multi-Site deployment is a distributed topology where the main application server is at a central site, and components like File Servers and Pollers are deployed at remote sites. This is ideal for geographically dispersed organizations.
Hardware Requirements
Main Site Server: The hardware requirements for the main site server are identical to those of a Standalone or Distributed deployment, depending on your chosen architecture at the central site.
Remote Site Servers: Each remote site requires dedicated servers for the following components:
File Server: See the "File/Relay Server for Patch Management" hardware table in the Standalone tab for guidance.
Critical Latency RequirementA high-speed, low-latency network connection between the Application Server and the File Server is essential. Insufficient bandwidth may slow down the deployment process, especially when handling large files or extensive deployments.
Poller Server: A dedicated server with Windows or Linux OS is required.
Network & System Prerequisites
Stable Connectivity: Continuous and stable network connectivity is required between the Main Site and all Remote Sites.
Firewall Configuration: Firewall rules must be configured to allow communication between the main server and the remote servers, typically over HTTPS (Port 443) or a custom port designated for the File Service and Poller Service.
Infrastructure Readiness:
- Main Site: A server (or servers) provisioned for the ServiceOps Application and Database.
- Remote Site: Dedicated servers for the File Server and Poller with sufficient storage, backup, and redundancy in place.
A High Availability (HA) deployment ensures service continuity by eliminating single points of failure. This setup involves a Master Server, a Slave Server, and an HA Observer/Proxy server.
Hardware Requirements
Master & Slave Servers: The hardware requirements for both the Master and Slave servers are identical to those of a Standalone deployment. You must provision the same configuration for both servers.
Servers: You need three separate servers: Master, Slave, and HA Observer.
RAM: Minimum 4GB of system RAM for each server.
CPU: Minimum four-core processor for each server.
Hard Disk: Minimum 100GB of hard disk space for each server.
Disk I/O: Minimum 150 Mbps+ continuous Disk I/O speed.
HA Observer / HA Proxy Server: This component requires its own server with the following minimum specifications:
- Minimum CPU: 4 Core
- Minimum RAM: 4 GB
- Minimum Storage: 100 GB
Port Requirements:
- Allow HTTPS (443) access from the Application Server to the HA Proxy.
- Allow SSH (port 22) access from the Observer to the Master and Slave servers.
- Allow PostgreSQL database (port 5432) access between the Master and Slave servers.
Network & System Requirements
- Stable Connectivity: Continuous and stable network connectivity is required between the Master, Slave, and HA Observer servers.
The ServiceOps application version must be identical on both Master and Slave servers to ensure compatibility and successful replication.
User Accounts: Use the same username and password for SSH on the Master, Slave, and HA Observer servers. The user must have a home directory and
sudopermissions.IP Address: Use static IP Addresses for the Master, Slave, and HA Proxy Servers.
Firewall Rules:
- Allow ICMP protocol (ping) between Master, Slave, and Observer servers.
- Allow SSH (port 22) access from the Observer to the Master and Slave servers.
- Allow PostgreSQL database (port 5432) access between the Master and Slave servers.
A Disaster Recovery (DR) deployment protects against data loss and minimizes downtime in case of a catastrophic failure at your primary data center. This involves replicating your primary Data Center (DC) site to a secondary DR site.
Hardware Requirements
- DC & DR Sites: The hardware requirements for both the DC and DR sites are identical to those of a Standalone deployment. It is crucial that the hardware configurations at both sites match to ensure consistency and a smooth failover.
Network & System Prerequisites
- Stable Connectivity: Continuous and stable network connectivity is required between the DC and DR sites.
The ServiceOps application version must be identical on both DC and DR servers to ensure compatibility and successful replication.
Firewall Rules: The SSH (port 22) and database (e.g., PostgreSQL port 5432) ports must be open for communication between the sites.
User Permissions:
- A consistent SSH username and password must be configured on both DC and DR servers.
- The SSH user must have
sudoprivileges and an entry in the/etc/sudoersfile. - The SSH user must have a dedicated home directory.
File Ownership: The ownership of the
/opt/flotomatedirectory must be set tofmtuser:fmtusergroup.chown -R fmtuser:fmtusergroup /opt/flotomateScript Management: On both DC and DR servers, any existing HA scripts (e.g.,
/opt/HA/slave.sh,/opt/HA/master.sh) should be backed up or renamed to avoid conflicts with DR scripts.mv /opt/HA/slave.sh /opt/HA/slave.sh.bkp
mv /opt/HA/master.sh /opt/HA/master.sh.bkp