RH436 – Red Hat High Availability Clustering — Lesson 2: Fencing, Resources, Groups, Clones, Constraints, and Failover Control

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing STONITH and resource agents.
• Implement and validate groups and clones, location constraints, and ordering and colocation using reviewable evidence.
• Evaluate the condition where a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ and select a proportionate corrective response.

Detailed Topics

• STONITH applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• resource agents applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• groups and clones applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• location constraints applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• ordering and colocation 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 a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ.

Hands-On Exercise

Complete a controlled Red Hat exercise covering Fencing, Resources, Groups, Clones, Constraints, and Failover Control 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 STONITH.
• 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 “a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ” 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 Fencing, Resources, Groups, Clones, Constraints, and Failover Control, explain the resulting platform behavior, and defend the outcome through the high-availability cluster build document, failover test evidence, storage design, and recovery runbook.