What are the supported "transport" types for corosync on RHEL 8 or later?
Environment
- Red Hat Enterprise Linux Server 8, 9, 10 (with the High Availability Add On)
Issue
What are the supported transport types for corosync on RHEL 8 or later?
Resolution
The only supported transport for corosync on RHEL 8 or later is knet. For more information then see: Support Policies for RHEL High Availability clusters - Transport Protocols.
A properly configured cluster for RHEL 8 or later should be using knet for the transport type for corosync. For example:
# grep transport /etc/corosync/corosync.conf
transport: knet
# corosync-cmapctl | grep "totem.transport "
totem.transport (str) = knet
If a RHEL 8 or later pacemaker cluster is not using knet for the transport type for corosync then it should be modified to use knet.
-
Edit the file
/etc/corosync/corosync.confand change thetransporton one node:transport: knet -
Sync the changes to all cluster nodes.
# pcs cluster sync
• Stop the cluster on all cluster nodes.
# pcs cluster stop --all
-
Start the cluster on all cluster nodes.
# pcs cluster start --all
Diagnostic Steps
In this example below the RHEL 8 cluster is using an unsupported transport type for corosync. The only supported transport type for corosync on RHEL 8 or later is knet. If it returns anything other than knet on RHEL 8 or later then the cluster is using an unsupported value for the transport type for corosync.
-
Check the configured type of
transportincorosyncconfiguration file.$ grep -h transport /etc/corosync/corosync.conf transport: udpu -
Check the configured type of
transportincorosyncat runtime$ corosync-cmapctl | grep "totem.transport " totem.transport (str) = udpu
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.