[DOCS-5891] Clarify networking requirements for Automation Created: 22/Jul/15  Updated: 24/Feb/16  Resolved: 22/Jul/15

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: mms-1.8

Type: Task Priority: Critical - P2
Reporter: Cailin Nelson Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 8 years, 30 weeks ago

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


Generated at Thu Feb 08 07:51:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.