Ops Manager System Requirements

Ops Manager Hardware Requirements

Every host that serves the Ops Manager application must meet the following hardware requirements. Note that connecting too many hosts to a single project may cause performance issues.

Ops Manager Application Database Hardware Requirements

The Ops Manager Application Database runs as a three-member replica set that runs on dedicated hosts.

Every host that serves the Ops Manager Application Database must meet the following hardware (physical or virtual) requirements. Note that connecting too many hosts to a single project may cause performance issues.

For the best performance, use:

• SSDs to store your Ops Manager Application Databases.

• The WiredTiger storage engine. For the differences between the WiredTiger and MMAPv1 storage engines, see the types of storage engines in the MongoDB manual.

Disk capacity estimates are approximate. The needed disk capacity can increase or decrease due to the number of databases being monitored.

Backup Daemon Hardware Requirements

Each host on which you activate the Backup Daemon must meet the following requirements plus those for Ops Manager.

Each host that serves an active Backup Daemon has the following hardware requirements:

The Backup Daemon should have at least 100 GB of available disk capacity.

Contact your MongoDB Account Manager to determine disk capacity and throughput requirements.

Backup Database Hardware Requirements

If you use Ops Manager Backup, you must provision hosts for the Backup Database.

Host requirements for the Backup Database vary, depending on whether you use a blockstore database or file system storage to store your snapshots. The Backup Database always holds oplog data.

If you store snapshots in the Backup Database, its hosts typically must have enough capacity to store 2 to 3 times the total backed-up production data size. Snapshots are compressed and de-duplicated at the block level in the blockstore.

Your specific requirements depend on your data compressibility and change rate. Contact your MongoDB Account Manager to help estimate the use case and workload-dependent storage requirements for your Backup Database hosts.

If you store snapshots in the Backup Database, each data-bearing member must meet the following requirements:

Contact your MongoDB Account Manager to determine disk capacity and throughput requirements.

If you will not store snapshots in the Backup Database, each data-bearing member must meet the following requirements:

Internet Site Access

If you configured Ops Manager to download binaries direct from the Internet, Ops Manager requires access to the following Internet sites over HTTPS using both IPv4 and IPv6 requests to the Internet:

Latency between Ops Manager and Backing Database Hosts

Connections between the Ops Manager Application host and its Application Database, Oplog, and blockstore replica sets must have the lowest possible network latency. With deployments exceeding 200 MongoDB hosts, latency between your Ops Manager Application components should be under 1 ms. Please contact MongoDB Support if you anticipate that your network environment cannot meet this requirement.

TCP Keepalive Setting

Many Ops Manager components connect to a running mongod process. These include:

• the application database,

• any backup databases, and

• any MongoDB databases that the MongoDB Agent manages.

The systems that host these components send data traffic to each other to verify an active connection. The TCP keepalive setting determines how often to run this check. Most systems use the default value of 7200 seconds (two hours).

The network connection may drop within that timeframe. Without an existing connection, Ops Manager must create a new connection to that mongod process. This can delay communication or result in network timeouts or socket errors. To prevent this issue, reduce the keepalive value to increase the verification checks. All Ops Manager components must use the same keepalive value.

To learn how to set this to the recommended value, see Does TCP keepalive time affect MongoDB Deployments? in the MongoDB Server Manual.

MongoDB and MongoDB Agent Host Access

Each MongoDB and MongoDB Agent host should self-identify as its FQDN to ensure reliable connectivity.

> hostname -f

mongodb.example.com

PS C:\> systeminfo | findstr /B /C:"Host" /C:"Domain"

Host Name:                 mongodb
Domain:                    example.com

Accessible Ports

The Ops Manager Application must be able to connect to users and MongoDB Agents over HTTP or HTTPS. MongoDB Agents must be able to connect to MongoDB client MongoDB databases.

Though Ops Manager only requires open HTTP (or HTTPS) and MongoDB network ports to connect with users and to databases, what ports are opened on a firewall depend upon what capabilities are enabled: encryption, authentication and monitoring.

This page defines which systems need to connect to which ports on other systems.

Ops Manager connects with a number of services. This page explains the ports that must be opened to deploy the various components used with an Ops Manager deployment.

The specific ports that must be open on any intermediate firewalls depend upon what capabilities are enabled, such as encryption, authentication, and monitoring.

click to enlarge

http://127.0.0.1:8090/health

{
  "mms_db": "OK",
  "backup_db": "OK"
}

/etc/hosts

/private/etc/hosts

%SystemRoot%\System32\drivers\etc\hosts

C:\Windows\System32\drivers\etc\hosts

127.0.0.1   localhost
10.15.0.5   opsmgr.example.dev
10.15.10.15 rs1.example.dev
10.15.10.16 rs2.example.dev
10.15.10.17 rs3.example.dev

Operating System Compatibility Matrices

Exec Options for /var Mount

Ops Manager requires the default exec option defined in /etc/fstab on the underlying host machine in order to run the required binaries stored in the volume backing the /var directory.

Ulimits Requirements for Ops Manager Application

The Ops Manager package automatically raises the following ulimits:

• Open files

• Maximum user processes

• Virtual memory

RHEL limits the maximum number of user processes to 1024. This overrides the general user process limit (ulimit -u) setting.

For the userid that runs Ops Manager (mongodb-mms by default), add soft and hard nproc (number of processes) entries to the /etc/security/limits.d/99-mongodb-nproc.conf user process configuration file. Use values that are larger than the RHEL 1024 user process limit.

mongodb-mms soft nproc 200000
mongodb-mms hard nproc 500000

If /etc/security/limits.d/99-mongodb-nproc.conf does not exist, create it. Use the contents of the /etc/security/limits.d/90-nproc.conf file as a template.

MongoDB Version for Ops Manager Application Database and Backup Database

For the following Ops Manager release series, you may run its backing databases on any of the following MongoDB versions:

Version support covers the full release series from the first to the last release.

To learn more about MongoDB versioning, see MongoDB Versioning in the MongoDB Manual.

Email Service

Install and verify an Email Server. Ops Manager needs an email server to send alerts and recover user accounts. You may use an SMTP Server or an AWS SES server. To configure your Email Server, see Email Delivery Method Configuration.

Many Linux host-oriented distributions include a local SMTP server by default. These include, but are not limited to:

• Postfix

• Exim

• Sendmail

Windows Server includes an SMTP relay with Internet Information Server.

You also may configure Ops Manager to send mail via third party providers. These include, but are not limited to:

• Gmail

• Sendgrid

Install fontconfig on Linux Hosts

When installing Ops Manager version 4.0.13 or later on Linux hosts, install the fontconfig package to enable data export from the Status tab to PDF or PNG format.

Client Web Browsers

To use Ops Manager, you must use one of the following supported browsers with Javascript enabled:

Ops Manager displays a warning on non-supported browsers.