Navigation

Configure Deployment to Have Limited Internet Access

In a default configuration, the Automation Agents and Backup Daemons access MongoDB binaries over the internet from MongoDB, Inc.

If your environment prevents granting all hosts in your MongoDB deployment access to the internet, you have two options:

Only Ops Manager Has Internet Access
Configure Ops Manager to download installers from the internet. Backup Daemons and managed MongoDB hosts can then download installers from Ops Manager.
No Hosts Have Internet Access
Configure Backup Daemons and managed MongoDB hosts to download installers only from Ops Manager. The installers need to uploaded to Ops Manager separately.

To manage MongoDB hosts without internet access, you must specify that:

  • Agents get the installers from: the Ops Manager Application Server, and
  • Ops Manager gets installers from: a Direct connection to MongoDB.

Ops Manager hosts download MongoDB installer binaries from the internet. MongoDB hosts with Automation Agents download these installers from the Ops Manager hosts and then install or upgrade MongoDB deployments.

The following tutorial outlines the steps to run Ops Manager with internet access when MongoDB hosts do not.

To manage MongoDB hosts and run Ops Manager without internet access, you must specify that:

  • Agents get the installers from: Ops Manager Application Server, and
  • Ops Manager gets installers from: Ops Manager Application Server Hard Drive.

For Backup Daemons or Automation Agents to install or upgrade MongoDB deployments, you must:

  • Download the MongoDB installer binaries for each edition, version, and platform you need to support from another internet-connected device.
  • Load the MongoDB installer binaries to each Ops Manager host.
  • Update the version manifest.

The following tutorial outlines the steps to run Ops Manager without internet access.

Considerations

MongoDB Community for Windows with SSL Incompatibility

Ops Manager supports MongoDB Community Edition for Microsoft Windows with SSL in the following versions:

  • MongoDB versions 3.2.12 or later
  • MongoDB versions 3.4.1 or later
  • MongoDB release series 3.6 and 4.0

To use earlier versions, you must download them from the MongoDB Download Center.

Prerequisites

Install Enterprise Dependencies (MongoDB Enterprise Only)

If you plan on running MongoDB Enterprise on Linux servers, then you must manually install a set of dependencies to each server before installing MongoDB. The MongoDB manual provides the appropriate command to install the dependencies. See the link for the server’s platform:

Required User Role to Change Mode

To configure internet access for Ops Manager and its agents, you must have Global Owner access to Ops Manager.

Required User Role to Change Mode

To configure internet access for Ops Manager and its agents, you must have Global Owner access to Ops Manager.

Determine which Binaries to Store Locally and Download

MongoDB Community and Enterprise installation binaries are available for all supported platforms and MongoDB versions.

Download binaries associated to each combination of MongoDB version, platform, and edition that you want to support in your current and prospective Ops Manager-managed deployments, including one for:

  • Each platform and version that your current and planned MongoDB deployments run.

  • Each platform and version along the upgrade path of any existing MongoDB deployments you want to upgrade.

    Example

    If you import an existing deployment of MongoDB 3.4 Community on Ubuntu 14.04 and want to upgrade it to MongoDB 4.0 Enterprise on Ubuntu 14.04, you must download and store all archived binaries for:

    • MongoDB 3.4 Community Edition
    • MongoDB 3.6 Community Edition
    • MongoDB 4.0 Community Edition
    • MongoDB 4.0 Enterprise Edition
  • If you are running backups, you need the MongoDB binary for the platform on which the Ops Manager Backup Daemon runs.

    Example

    If you are running a MongoDB replica set on MongoDB 3.6.8 on a set of Ubuntu hosts and running Ops Manager on Windows, you must have archived binaries of MongoDB 3.6.8 for Ubuntu and for Windows.

  • If you are running queryable backups, you need the Enterprise edition of the MongoDB version that your deployment runs.

    Example

    If you are running a MongoDB replica set on MongoDB 3.6.8 on a set of Ubuntu hosts and want to query backups from an Ops Manager install on Windows, you must have archived binaries of MongoDB Community 3.6.8 for Ubuntu and MongoDB Enterprise 3.6.8 Windows.

Configure Automation Agents to Use Local Downloads

1

Set the source for Ops Manager and its Agents to install binaries to the Ops Manager Application Server.

  1. Click Admin in the upper right corner to open system administration.

  2. From the General tab, click Ops Manager Config.

  3. Click the Miscellaneous tab at the top of the page.

  4. Scroll to the MongoDB Version Management heading.

  5. Select the following settings:

    Option Action
    Agents get the installers from: under Installer Download Source

    Select Ops Manager Application Server.

    All necessary installers are downloaded from Ops Manager Application Servers. Agent hosts do not need an internet connection.

    Ops Manager gets installers from: under Installer Download Source

    Select Direct connection to MongoDB.

    Ops Manager fetches installation binaries from MongoDB, Inc. and serves them to Agents. Ops Manager Application hosts require an internet connection.

    Note

    This option appears if Agents get the installers from: is set to Ops Manager Application Server.

    Versions Directory

    Leave this value to the plaform default unless you need to change to meet a requirement for your environment.

    The default locations for the Versions Directory depend on your Ops Manager host platform:

    Platform Versions Directory Default Path
    RHEL, Ubuntu /opt/mongodb/mms/mongodb-releases
    Linux Archive <userSelected>/mongodb-releases
    Windows C:\MMSData\MongoDBReleases

    The Ops Manager Application expects the MongoDB binaries to be stored in this directory on every Ops Manager host.

    Backup Versions Auto Download Select true unless your Backup Daemon and Ops Manager Application run on different platforms (chip architectures, operating systems, or operating system versions). If they run on separate platforms, select false.
    Backup Versions Auto Download Enterprise Builds Select true if you want the Backup Daemon to download MongoDB Enterprise builds as well as MongoDB Community builds.
    Required Module for Backup Select which build of MongoDB you want the Backup Daemon to use for the head database. Select Enterprise Required if you want the Backup Daemon to download only MongoDB Enterprise builds.
2

Specify which versions the Automation Agents can download per project.

  1. In Ops Manager, click Back To Project in the upper left to exit system administration.
  2. Click the Project link at the top of the page and select the desired project.
  3. Click Deployment, then the More drop-down list, then Version Manager.
  4. Select the checkboxes for the versions of MongoDB that you have made available on the Ops Manager Application host.

Important

Download and place the archived binaries for the selected versions in the Versions Directory. For Ops Manager deployments operating in Local Mode, Ops Manager fails a pre-flight check when starting if one or more archived binaries are missing.

3

Review and approve your changes.

Ops Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.
  2. Otherwise, click Cancel and you can make additional changes.

Configure All Hosts to Use Local Downloads

1

Set the source for Backup Daemons and its Agents to install binaries to the Ops Manager Application Server.

  1. Click Admin in the upper right corner to open system administration.

  2. From the General tab, click Ops Manager Config.

  3. Click the Miscellaneous tab at the top of the page.

  4. Scroll to the MongoDB Version Management heading.

  5. Select the following settings:

    Option Action
    Agents get the installers from: under Installer Download Source

    Select Ops Manager Application Server.

    All necessary installers are downloaded from Ops Manager Application Servers. Agent hosts do not need an internet connection.

    Ops Manager gets installers from: under Installer Download Source

    Select Ops Manager Application Server Hard Drive.

    An Ops Manager administrator provides installers from the MongoDB Download Center into the Versions Directory. Ops Manager serves them to Agent hosts. The Version Manifest must be updated manually. No hosts in the deployment require an internet connection.

    Note

    This option appears if Agents get the installers from: is set to Ops Manager Application Server.

    Versions Directory

    Leave this value to the plaform default unless you need to change to meet a requirement for your environment.

    The default locations for the Versions Directory depend on your Ops Manager host platform:

    Platform Versions Directory Default Path
    RHEL, Ubuntu /opt/mongodb/mms/mongodb-releases
    Linux Archive <userSelected>/mongodb-releases
    Windows C:\MMSData\MongoDBReleases

    The Ops Manager Application expects the MongoDB binaries to be stored in this directory on every Ops Manager host.

    Backup Versions Auto Download Select true unless your Backup Daemon and Ops Manager Application run on different platforms (chip architectures, operating systems, or operating system versions). If they run on separate platforms, select false.
    Backup Versions Auto Download Enterprise Builds Select true if you want the Backup Daemon to download MongoDB Enterprise builds as well as MongoDB Community builds.
    Required Module for Backup Select which build of MongoDB you want the Backup Daemon to use for the head database. Select Enterprise Required if you want the Backup Daemon to download only MongoDB Enterprise builds.
2

Download the required MongoDB archives.

Using a computer connected to the Internet, go to the MongoDB Download Center and download the MongoDB binary archives for the appropriate platforms and versions.

Binaries are stored as compressed archives (.tgz for macOS or Linux and .zip for Windows).

Downloading Archives with Microsoft Internet Explorer and Edge Browsers

If you download a binary archive using Microsoft Internet Explorer or Edge, the archive downloads with a .gz extension instead of a .tgz extension. You must change this file extension to .tgz before continuing.

If you do not have a list of which versions you require, return to the Prerequisites section of this tutorial and review the Determine which Binaries to Store Locally and Download section.

To download a Community Edition:

  1. Go to the Community Server tab in the Download Center.

  2. Click on the tab for the desired platform.

  3. In the Version list, click the desired platform version.

  4. To download the latest stable version, click Download.

    For the current stable version, click the Download button and in the dialog that appears, click on the archive link.

  5. To download the older versions, click All Version Binaries.

  6. Download the archive file for each MongoDB host platform that Ops Manager manages.

To download an Enterprise Edition:

  1. Go to the Enterprise Server tab in the Download Center.

  2. Click on the tab for the desired platform.

  3. In the Version list, click the desired platform version.

  4. To download the latest stable version, click Download.

    For the current stable version, click the Download button and in the dialog that appears, click on the archive link.

  5. To download the older versions, click Archived Releases.

    For each platform and MongoDB version you want to download, click the link to the right of the Archive label.

3

Populate all Ops Manager hosts with the necessary MongoDB binaries and archives.

On all your Ops Manager hosts, including those with enabled Backup Daemons, you must copy all of the archived binaries to the directory specified in the Versions Directory. This directory stores all of the MongoDB archived and extracted binaries that Ops Manager needs to install and upgrade MongoDB deployments and head databases.

4

Ensure that the Ops Manager Linux user can read files in the Versions Directory. (Linux only)

On a Linux platform, the mongodb-mms user needs the read permissions to the Versions Directory.

  1. Change ownership of all files and directories in the Versions Directory to mongodb-mms.

    sudo chown -R mongodb-mms:mongodb-mms <path-to-the-versions-directory>/*
    
  2. Change permissions on all the files under the Versions Directory to allow the:

    • Owner to read and write them
    • Group to read them

    When you set these permissions, Ops Manager can read and extract the archived binaries. Do not remove the execute permission from any directories under the Versions Directory. If you did, the Backup Daemon cannot access any files inside those directories.

    sudo chmod -R 640 <path-to-the-versions-directory>/*.tgz \
      <path-to-the-versions-directory>/*.zip
    

If these steps were successful, the resulting list of the Versions Directory should look something like this:

-rw-r----- 1 mongodb-mms mongodb-mms 116513825 Apr 27 15:06 mongodb-linux-x86_64-2.6.9.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  51163601 May 22 10:05 mongodb-linux-x86_64-amazon-3.0.3.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  50972165 May 22 10:06 mongodb-linux-x86_64-suse12-3.6.4.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  95800685 Apr 27 15:05 mongodb-linux-x86_64-enterprise-amzn64-2.6.9.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  50594134 Apr 27 15:04 mongodb-linux-x86_64-enterprise-amzn64-3.0.2.tgz
-rw-r----- 1 mongodb-mms mongodb-mms  50438645 Apr 27 15:04 mongodb-linux-x86_64-enterprise-suse12-3.6.4.tgz
drwxrwx--- 1 mongodb-mms mongodb-mms      4096 Apr 27 15:04 mongodb-linux-x86_64-enterprise-suse12-3.6.4

Repeat these steps on each Ops Manager host.

5

Update the version manifest for Ops Manager on each Ops Manager host.

Update the Version Manifest using your Web Browser.

The version manifest provides Ops Manager with a list of all released MongoDB versions available to your Ops Manager hosts.

  1. Click the Update MongoDB Version Manifest from MongoDB, Inc. button.
  2. The version manifest should update automatically.
Update the Version Manifest offline.

If the update via the web browser does not work, you need to copy and paste the version manifest to your Ops Manager hosts.

  1. From a computer that can access both the Internet, download the version manifest from https://opsmanager.mongodb.com/static/version_manifest/4.0.json.
  2. Transfer the version manifest to a computer that can connect to your Ops Manager Application.
  3. Open the manifest JSON file.
  4. Select all of the contents and copy them to the clipboard.
  5. Log in to Ops Manager.
  6. Click Admin in the upper right corner to open system administration.
  7. Click the General tab.
  8. Click Version Manifest.
  9. Click the Update MongoDB Version Manifest button.
  10. Paste the version manifest in the box.
  11. Click Save.
6

Specify which versions the Automation Agents can download per project.

  1. In Ops Manager, click Back To Project in the upper left to exit system administration.
  2. Click the Project link at the top of the page and select the desired project.
  3. Click Deployment, then the More drop-down list, then Version Manager.
  4. Select the checkboxes for the versions of MongoDB that you have made available on the Ops Manager Application host.

Important

For the selected versions, ensure that you have downloaded and placed the archived binaries in the Versions Directory. Otherwise, Ops Manager fails a pre-flight check when starting in Local Mode.

7

Review and approve your changes.

Ops Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.
  2. Otherwise, click Cancel and you can make additional changes.