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

Add DLM port number #232

Merged
merged 1 commit into from
Jul 20, 2022
Merged

Add DLM port number #232

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
6 changes: 3 additions & 3 deletions xml/ha_storage_basics.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,13 @@
To avoid single points of failure, redundant communication paths are important
for &ha; clusters. This is also true for DLM communication. If network bonding
(Link Aggregation Control Protocol, LACP) cannot be used for any reason, we
highly recommend to define a redundant communication channel (a second ring)
highly recommend defining a redundant communication channel (a second ring)
in &corosync;. For details, see <xref
linkend="pro-ha-installation-setup-channel2"/>.
</para>
<para>
Depending on the configuration in &corosync.conf;, DLM then decides
whether to use the TCP or SCTP protocol for its communication:
DLM communicates through port 21064 using either the TCP or SCTP protocol,
depending on the configuration in &corosync.conf;:
</para>
<itemizedlist>
<listitem>
Expand Down