IBM AIX 7.3 – Common Problem 109 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

PowerHA reports two active nodes owning the same RG.

Environment & Reproduction

Heartbeat network partition or storage fencing failure.

Root Cause Analysis

Cluster manager (clstrmgrES) cannot reach peer to negotiate.

Quick Triage

Run clRGinfo -p and cltopinfo to inspect RG ownership.

Step-by-Step Diagnosis

Check /var/hacmp/log/hacmp.out and clcomd logs for split events.

Solution – Primary Fix

Fence loser, run clRGmove to move RG to chosen node, then sync cluster.

Solution – Alternative Approaches

Bring one node offline via clstop -gr if storage fencing missing.

Verification & Acceptance Criteria

clRGinfo shows single online owner; apps respond on VIP.

Rollback Plan

If wrong node won, planned failover with clRGmove -m -i.

Prevention & Hardening

Add a tiebreaker disk and redundant heartbeat networks.

Related Errors & Cross-Refs

Often co-occurs with cl_lvm errors and LVM quorum loss.

Related tutorial: View the step-by-step tutorial for aix-7.3.

View all aix-7.3 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

IBM Docs: PowerHA SystemMirror Admin.