Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fixes #17837: Missing doc about root-relay communication flows #751

Merged
merged 1 commit into from Jun 25, 2020
Merged

Fixes #17837: Missing doc about root-relay communication flows #751

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
24 changes: 10 additions & 14 deletions src/reference/modules/installation/pages/requirements.adoc
View file
Open in desktop
Expand Up @@ -11,23 +11,19 @@ Internet Explorer is not supported.

The following network flows are used by Rudder for regular operations. Make sure your firewalls allow these connections.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"In the following table, the port is the destination port"


Please bear in mind that a central Rudder server, called root server, requires network flows from both the 'Root server' and 'Policy server' sections below.

.Network Flows
[cols="<.^,<.^,<.^,<.^", options="header"]
[cols="<.^2,<.^2,<.^1,<.^3", options="header"]
|=======================
|To|From|Port|Usage
|Root Server|User or API client| *tcp/443* (https) | Access Web interface/API
.5+|Policy Server |Linux/AIX Node < 6.0|_udp/514 (optional)_ (or _tcp/514_) |Send reports
|Linux/AIX Node >= 6.0 .2+| *tcp/443* (https/WebDAV) | Send reports
.2+|Linux/AIX Node | Send inventories
| *tcp/5309* |Fetch policies
|Windows Node | *tcp/443* (https/WebDAV) | Send inventories and fetch policies
|Linux/AIX Node | Policy Server | _tcp/5309 (optional)_ | Trigger remote agent run
|From|To|Destination|Usage
|User or API client|Root| *tcp/443* | Access Web interface/API
|Node .2+|Relay/Root | *tcp/443* | Send reports and inventories, fetch files
|Linux/AIX node | *tcp/5309* |Fetch policies
.2+|Relay .2+|Root | *tcp/443* | Send reports and inventories, fetch files
| *tcp/5309* |Fetch policies
|Relay/Root|Linux/AIX node | _tcp/5309_ .2+| *[optional]* Trigger remote agent run
|Root|Relay|_tcp/443_
|=======================

Note: The policy server is the server configured to manage the node, and can be
either a root server or a relay server.
NOTE: If you still have pre-6.0 agents, or use the syslog-only report mode, you also need to have *udp/514* (or *tcp/514* depending on what you configured) open from nodes to relays or root, and from relays to root server.

=== Security

Expand Down