RH436 – Red Hat High Availability Clustering — Lesson 1: High-Availability Concepts, Pacemaker, Corosync, Quorum, and Cluster Setup

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing availability design and Pacemaker.
• Implement and validate Corosync, quorum, and cluster creation using reviewable evidence.
• Evaluate the condition where the observed result differs from the approved configuration because a prerequisite, permission, dependency, or sequence was missed and select a proportionate corrective response.

Detailed Topics

• availability design applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• Pacemaker applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• Corosync applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• quorum applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• cluster creation applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces an infrastructure team designing a resilient clustered service with controlled failover and shared storage. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the high-availability cluster build document, failover test evidence, storage design, and recovery runbook. It also tests the exception where the observed result differs from the approved configuration because a prerequisite, permission, dependency, or sequence was missed.

Hands-On Exercise

Complete a controlled Red Hat exercise covering High-Availability Concepts, Pacemaker, Corosync, Quorum, and Cluster Setup and preserve the verified result in the high-availability cluster build document, failover test evidence, storage design, and recovery runbook.

1. Confirm scope, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording commands, settings, outputs, events, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, rollback, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences availability design.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the high-availability cluster build document, failover test evidence, storage design, and recovery runbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check prerequisites, identity, configuration order, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “the observed result differs from the approved configuration because a prerequisite, permission, dependency, or sequence was missed” as a hypothesis until commands, logs, settings, and retest outcomes confirm the cause.

Validation Checklist

• Required platform components, identities, permissions, settings, and dependencies are present.
• The high-availability cluster build document, failover test evidence, storage design, and recovery runbook connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply High-Availability Concepts, Pacemaker, Corosync, Quorum, and Cluster Setup, explain the resulting platform behavior, and defend the outcome through the high-availability cluster build document, failover test evidence, storage design, and recovery runbook.