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.

You need binaries for each MongoDB version that corresponds to deployments that you manage or plan to manage. For example:

  • 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. For Version Manifest Source, select Local.
  5. Note the directory specified in Versions Directory. This is the directory on your Ops Manager servers where you will store the MongoDB binaries.
  6. For Backup Version Auto Download, select false.

Note

When running in Local Mode, ensure that both the Version Manifest Source is Local and the Backup Version Auto Download is false.

2

Download the required MongoDB archives.

Go to 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).

Note

See Determine which Binaries to Store Locally and Download to review which versions you require.

To download a Community Edition:

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

  2. Select the version. The default version is the latest stable version.

    To select an older version, click Previous Releases or All Version Binaries link.

  3. Download the archive for your platform.

To download an Enterprise Edition:

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

  2. Select the version. The default version is the latest stable version.

    To select an older version, click the Archived Releases link.

  3. Download the archive for your platform.

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

    For older versions, click the Archived Releases link. For your platform and MongoDB version, click the link for the Archive.

3

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

On all your Ops Manager servers, including those with enabled Backup Daemons:

  1. Copy all of the archived binaries to the directory specified in Versions Directory. The versions directory stores all of the archived and extracted MongoDB binaries Ops Manager needs to install and upgrade MongoDB deployments.

    Note

    Automation uses the archived binaries; Backup uses the extracted binaries. Both must be available in the versions directory.

    By default, the versions directory is found in the following locations on the following platforms.

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

    To specify a different path for your versions directory, use the Versions Directory setting on your Ops Manager application.

  2. Navigate to the versions directory.

  3. Extract all of the archived binaries needed for the system’s backup daemon. The extracted archive creates a subdirectory that uses the following naming convention: mongodb-<platform>-<architecture>-<version>.

    Important

    Ensure that the binaries match the Backup Daemon’s operating system and reflect the latest in the series for each MongoDB version in your deployments. For example, if the MongoDB version of your deployment is v3.2, latest in the series would be 3.2.x where x is the latest revision version number.

4

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

The mongodb-mms user needs the read permissions to the versions directory.

Example

On a Linux platform, you should issue the chown command to change ownership for all files in the directory to mongodb-mms:

sudo chown -R mongodb-mms:mongodb-mms <path-to-the-versions-directory>/*

Set the permissions to:

  • read and write for the owner
  • read for the group
  • none for all

This enables Ops Manager can correctly read and extract the archived binaries.

sudo chmod -R 640 <path-to-the-versions-directory>/*

The resulting listing of the versions directory should look 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
5

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

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

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

Copy and paste the contents the version manifest into the Ops Manager application on each Ops Manager host. (Optional)

If the automatic update does not work, you need to copy and paste the version manifest to your Ops Manager servers.

  1. From a computer that can access both the Internet and the Ops Manager servers, download the version manifest from https://opsmanager.mongodb.com/static/version_manifest/3.4.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.
7

For each group, specify which versions are available for download by Automation Agents.

  1. In Ops Manager, click Back To Group in the upper left to exit system administration.
  2. Click the Group link at the top of the page and select the desired group.
  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 server.

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.

8

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.