[DOCS-7381] Firewall configuration docs incomplete Created: 09/Mar/16  Updated: 27/Jul/16  Resolved: 19/Jul/16

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Andrew Davidson Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File NetworkPorts.png     PNG File NetworkPorts.png    
Participants:
Days since reply: 7 years, 30 weeks, 2 days ago
Epic Link: Cloud Docs Reorg
Story Points: 2

 Description   

The page (https://docs.opsmanager.mongodb.com/current/reference/firewall-configuration/) needs some work:

Nothing about the required ports needed for the managed nodes and agents shows on this page. We should bring in generalized content from https://docs.opsmanager.mongodb.com/current/core/requirements/#ec2-security-groups into this page. Ideally we would have a diagram as well explaining what port needs to be accessible to what over the network.

This page also does not remind the user that if SSL (HTTPS) is used, then the ports listed may not be used.



 Comments   
Comment by Andrew Davidson [ 18/Jul/16 ]

tony.sansone Love the diagram. Two tweaks
1) Ops Manager does not need to reach in to the database nodes (the agents always reach in to Ops Manager from the database node machines instead).
2) I think it makes sense to show instead of "MongoDB client Database" something like "MongoDB Cluster Member 1", "MongoDB Cluster Member 2", "MongoDB Cluster Member N" e.g. like stacked cards on the diagram --> where each of those nodes can reach each other on the MongoDB ports.

Comment by Cory Mintz [ 18/Jul/16 ]

Looks good.

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