System Requirements

Machine Specifications

Recommended system requirements are based on SIP best practices. Failing to meet these recommendations can lead to possible performance issues.

We recommend accessing SIP using one of the following supported browsers: Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari with a minimum screen resolution of 1280 x 800.

When first installing FMOS, the initial configuration wizard will check the local system to ensure it meets the recommended system requirements. These requirements provide a baseline for all deployments. When planning the deployment, consider the following guidelines:

  • Servers with the database (DB) role will require very large amounts of RAM, especially when generating reports or running assessments.
  • Servers with the application server (AS) role will use a large amount of RAM and CPU time, and demand will increase as the number of users grows.
  • Servers with the data collector (DC) role will use large amounts of RAM and CPU time, and demand will increase as the number of monitored devices grows.

These are the recommended system requirements.

Servers store configuration settings, change history, usage data, logs, and backups for all your devices. Because no two environments are alike, our storage recommendations are designed to accommodate a wide range of sizes and complexities. While this may exceed your environment's immediate needs, it ensures we can support even the most demanding scenarios.

Full Install

Machines running the full or cloud variant of FMOS must have at least these specifications:

  • CPU: 32 cores, 3.2 GHz

  • RAM: 96 GB DDR4-2666 with ECC

  • Storage: 1200 GB (SAS, 15K RPM HDD or SSD, RAID 10)

Many VMs require additional disk space be created prior to installing FMOS. You will need to either edit the disk size and make it the recommended size (500 GB) or add a second disk size of 250 GB.

DC Only Install

Machines running the dconly variant of FMOS must have at least these specifications:

  • CPU: 24 cores, 3.4 GHz

  • RAM: 64 GB DDR4-2666 with ECC

  • Storage: 240 GB (SATA or SAS, 15K RPM or SSD, RAID 1)

Network Topology

When deploying multiple servers, consider the following guidelines for best overall performance:

  • All servers holding the application server role must be on the same network segment.
  • If the application server and database roles are held by separate servers, those servers should be on the same network segment, with a very high bandwidth connection between them.
  • Servers holding the data collector role should be located logically near the devices they monitor.
  • Application servers must be able to resolve the database server by fully qualified domain name (FQDN).
  • Data collector servers must be able to resolve application servers by FQDN.
  • A default gateway must be configured on all servers.

Database Server (DB)

  • ICMP/ICMPv6

  • IP protocol 50 (ESP)

  • TCP port 443 (HTTPS)

  • TCP port 5432 (PostgreSQL)

  • TCP port 55555 (FMOS Control Panel)

  • UDP port 500 (ISAKMP)

  • UDP port 4500 (IPsec-NAT-T)

Application Server (AS)

  • ICMP/ICMPv6

  • IGMP

  • IP protocol 50

  • TCP port 443 (HTTPS)

  • TCP port 61617 (ActiveMQ)

  • UDP port 500 (ISAKMP)

  • UDP port 4500 (IPsec-NAT-T)

  • Multicast UDP port 6155 (ActiveMQ Cluster Member Discovery)

Data Collector (DC)

  • ICMP/ICMPv6

  • UDP port 514 (Syslog) (as needed)

  • TCP port 1470 (Syslog) (as needed)

  • TCP port 5150 (DC cluster) (as needed)

Outgoing external domains that SIP connects to after installation

Domain Purpose
https://fmosupdate.firemon.com Support file upload
news.fmos.firemon.com FMOS News Service
https://usercenter.firemon.com account management, user guides, update downloads
https://nvd.nist.gov/feeds/json/cve/ CVE data for Risk Analyzer users