Support Policies for RHEL High Availability clusters - corosync

Updated -

Contents

Overview

Applicable Environments

  • Red Hat Enterprise Linux (RHEL) with the High Availability Add-On

Useful References and Guides

Introduction

This guide lays out the policies applicable to Red Hat's support for the RHEL High Availability cluster software in the area of the corosync component and its related settings. Users of the RHEL High Availability product should adhere to these policies in order to be eligible for assistance from Red Hat with the appropriate product support subscriptions.

Policies

Usage outside of a RHEL High Availability cluster: Red Hat only supports usage of corosync in the context of a RHEL High Availability cluster utilizing the full cluster stack that is a part of the High Availability Add-On. Specifically:

  • RHEL 7 and 8: Red Hat only provides support for the corosync component when used in conjunction with pacemaker.
  • RHEL 6: Red Hat only provides support for the corosync component when used in conjunction with cman - regardless of whether pacemaker is used.
    • NOTE: Red Hat does NOT provide support for running RHEL 6 clusters with pacemaker directly using corosync without cman. cman is required in RHEL 6 for support from Red Hat.

Cluster deployments that use corosync in a stand-alone manner will not receive support from Red Hat.

totem token limits: Red Hat places the following supported limits on the totem token setting that controls the timing and timeouts of ORF tokens (aka heartbeats) within a cluster:

  • RHEL 7, 8 and 9: Maximum 300000 ms (300 s), no minimum
  • RHEL 6: Maximum 300000 ms (300 s), minimum 5000 ms (5 s)

Comments