Skip to content

Bug 1518471 Added info about port 1936 #6881

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

Merged
bfallonf merged 1 commit into from
Dec 19, 2017
Merged

Bug 1518471 Added info about port 1936 #6881

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions install_config/install/prerequisites.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -592,9 +592,10 @@ Only required to be internally open on master hosts.

| *1936*
|TCP
| For router statistics use. Required to be open when running the template
router to access statistics, and can be open externally or internally to
connections depending on if you want the statistics to be expressed publicly.
| (*Optional*) Required to be open when running the template router to access
statistics. Can be open externally or internally to connections depending on if
you want the statistics to be expressed publicly. Can require extra
configuration to open. See the Notes section below for more information.
Copy link
Copy Markdown
Contributor

@gaurav-nelson gaurav-nelson Dec 19, 2017

Choose a reason for hiding this comment

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

Would it makes sense to xref to notes section? (if it requires too much scrolling)

Copy link
Copy Markdown
Author

@bfallonf bfallonf Dec 19, 2017

Choose a reason for hiding this comment

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

It's barely a roll away, so I figured it was OK not to. It's on the same screen even.


| *4001*
|TCP
Expand Down Expand Up @@ -626,6 +627,12 @@ connections, and is only required if you have clustered etcd.
* When deployments are using the SDN, the pod network is accessed via a service proxy, unless it is accessing the registry from the same node the registry is deployed on.
* {product-title} internal DNS cannot be received over SDN. Depending on the detected values of `*openshift_facts*`, or if the `*openshift_ip*` and `*openshift_public_ip*` values are overridden, it will be the computed value of `*openshift_ip*`. For non-cloud deployments, this will default to the IP address associated with the default route on the master host. For cloud deployments, it will default to the IP address associated with the first internal interface as defined by the cloud metadata.
* The master host uses port *10250* to reach the nodes and does not go over SDN. It depends on the target host of the deployment and uses the computed values of `*openshift_hostname*` and `*openshift_public_hostname*`.
* Port *1936* can still be inaccessible due to your iptables rules. Use the following to configure iptables to open port *1936*:
+
----
# iptables OS_FIREWALL_ALLOW -p tcp -m state --state NEW -m tcp \
--dport 1936 -j ACCEPT
----

.Aggregated Logging
[cols='2,1,8']
Expand Down