Navigation

Configure Local Mode for Ops Manager Servers without Internet Access

Overview

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

To run Automation Agents or Backup Daemons on servers that do not have internet access, you must run Ops Manager in Local Mode. This requires that you manually download the MongoDB binaries for each version and platform you need to support and that you update the version manifest.

The following tutorial outlines the steps to run in Local Mode.

Note

The MongoDB Community Edition for Microsoft Windows with SSL support is incompatible with Local Mode.

Prerequisites

Required Access

To configure Local Mode, you must have Global Owner access to Ops Manager.

Determine which Binaries to Store Locally and Download

Note

The MongoDB Community Edition for Microsoft Windows with SSL support is incompatible with Local Mode.

Download the binaries associated to each MongoDB version you want to support in your Ops Manager-managed deployments:

  • To import existing deployments into Ops Manager, you need versions of the binaries that correspond to these deployments.

  • To create via Ops Manager Automation new deployments, you need versions of the binaries that correspond to these deployments.

  • To upgrade existing deployment to a new version via Ops Manager, you need both the current version, upgrade version, and versions used in intermediary step or steps.

    Example

    If you import an existing deployment of MongoDB 2.6 Community and want to upgrade it to MongoDB 3.0 Enterprise, you must download and store all archived binaries for:

    • MongoDB 2.6 Community Edition
    • MongoDB 3.0 Community Edition
    • MongoDB 3.0 Enterprise Edition

You do not need to download the archived MongoDB binary for every platform, only the one(s) in your current and planned MongoDB deployments.

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:

Configure Local Mode

1

Set Ops Manager to Local Mode.

  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 button at the top of the page.

  4. Select the following settings:

    Option Action
    Version Manifest Source Select Local.
    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.

    MongoDB version for Backup Daemon and Ops Manager must be same platform

    If the Agents and the Backup Daemon run on a “mixed environment” of different host platforms, you must manage the installation and upgrade of the MongoDB version for the Backup Daemon manually. If the Backup Daemon manages downloading and extracting the MongoDB version for the head database, it could try to install or upgrade an incompatible binary in a mixed environment.

    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.
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 Mac OS X, Linux, or Solaris 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.

To review which versions you require, see Determine which Binaries to Store Locally and Download.

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.

Optional: Extract MongoDB binaries on Backup Daemon host

Important

Skip these steps if you set Backup Version Auto Download to true.

  1. Login to the Ops Manager host that runs the Backup Daemon.

  2. Change to the Versions Directory into which you copied the archived binaries.

    cd /opt/mongodb/mms/mongodb-releases
    
  3. Extract all of the archived binaries needed for Ops Manager’s Backup Daemon. When extracted, the archive creates a subdirectory that uses the following naming convention:

    mongodb-<platform>-<chip-architecture>-(edition)-<platform-version>-<mongodb-version

    Example

    mongodb-linux-x86_64-enterprise-suse11-3.6.2.tgz
    

The extracted binaries must match the Backup Daemon’s platform and must be the latest in the series for each MongoDB version in your deployments.

Example

If the MongoDB version of your deployment is v3.6, latest in the series would be 3.6.x where x is the latest revision version number.

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-suse11-3.0.3.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-suse11-3.0.2.tgz
drwxrwx--- 1 mongodb-mms mongodb-mms      4096 Apr 27 15:04 mongodb-linux-x86_64-enterprise-suse11-3.0.2

Repeat these steps on each Ops Manager host.

5

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

Configure Automatic Updates for the Version Manifest.

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.

Configure Manual Updates for the Version Manifest.

If the automatic update 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 and the Ops Manager hosts, download the version manifest from https://opsmanager.mongodb.com/static/version_manifest/3.6.json.
  2. Open the manifest JSON file.
  3. Select all of the contents and copy them to the clipboard.
  4. In Ops Manager, click Admin in the upper right corner to open system administration.
  5. Click the General tab.
  6. Click Version Manifest.
  7. Click the Update MongoDB Version Manifest from MongoDB, Inc. button.
  8. Paste the version manifest.
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 both the archived and extracted binaries in the Versions Directory. Otherwise, Ops Manager fails a pre-flight check when starting in Local Mode. See also Start Ops Manager When All Versions Are Not Downloaded.

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.