...
The machine hosting the FeedMaster nodes needs to have those ports open on the local firewall, and the other Groundplex nodes need to allow outbound requests to the FeedMaster nodes on those ports.
Groundplex Nodes
Name
Every Snaplex requires a name, for example, ground-dev or ground-prod. In the SnapLogic Designer, you can choose which Snaplex where Pipelines are executed. The Self-managed Snaplex configuration also has an Environment variable associated with it, for example, dev or prod. When you configure the nodes for the Snaplexyour Groundplex, you must set the jcc.environment to the Environment value that you have configured for the Snaplex.
The hostname of the system used by a Snaplex a Groundplex can not use have an underscore (_) in its name as per DNS standards. Avoid special characters as well.
...
The nodes need to communicate to with each other on the following ports: 8081, 8084, and 8090.
The nodes should have a reliable, low-latency network connection between them.
The nodes should be homogeneous in that they should have similar CPU and memory configurations, as well as access to the same network endpoints.
...
The Pipeline Execute Snap communicates directly with neighboring JCC nodes in a Snaplex to start child Pipeline executions and send documents between parent and child Pipelines.
The data displayed in Data Preview is written to and read from neighboring JCC nodes in the Snaplex.
The requests and responses made in Ultra Pipelines are exchanged between a FeedMaster node and all of the JCC nodes in a Snaplex.
A Ground Triggered Task (invoked from a Groundplex) can be executed on a neighboring JCC node due to load - balancing—in which case, the prepare request and the bodies of the request and response are transferred between nodes.
...