Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-5891

Clarify networking requirements for Automation

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical - P2 Critical - P2
    • mms-1.8
    • None
    • Cloud Manager
    • None

    Description

      In this paragraph:

      https://docs.opsmanager.mongodb.com/current/tutorial/add-existing-host-to-automation/#server-networking-access

      we correctly mention that every server must be able to resolve every other server using the FQDN.

      However, we do not mention that from every server in the deployment you must be able to contact every MongoDB process in the deployment.

      That is, if I have the following servers and MongoDB processes:

      • a.example.com: a.example.com:27017
      • b.example.com: b.example.com:27018

      Then the Automation Agent on a.example.com, must be able to reach the MongoDB process on port 27018 on b.example.com and the Automation Agent on b.example.com must be able to reach the MongoDB process on port 27017 on a.example.com.

      This rule holds regardless of what type of MongoDB process is involved (mongos, config server, replica set node, standalone, etc.).

      Attachments

        Activity

          People

            allison.moore@mongodb.com Allison Reinheimer Moore
            cailin.nelson@mongodb.com Cailin Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              8 years, 30 weeks ago