DDI resilience: shared infrastructure failure domains
Both DDI appliances fail during one rack power test. The inventory says “HA pair”. The rack has expressed a different architectural opinion.
What you’ll practise
Trace the supplied evidence, challenge alternative explanations, and choose a safe next action. Use the topology and private notebook to document your reasoning.
Lab scope: Synthetic approved resilience exercise. Test power isolation affects a single rack PDU. No claim is made that application HA can replace physical fault separation.
Validation: Original synthetic operational lab; not a reproduced vendor defect
DHCP says yes.
DNS says yesterday.
A laptop moved networks. Its name didn’t. Find out who’s telling the truth — and what you should check next.
Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.
New lease.
Old address.
Same confused user.
10.62.4.27 ✓↓ six minutes and three cache flushes later09:36 / DNS ANSWER10.61.4.27 ?“Have you tried flushing it again?”
The fourth time is not a strategy.
Troubleshooting guide
Recognise the symptoms
Both DDI appliances fail during one rack power test. The inventory says “HA pair”. The rack has expressed a different architectural opinion.
Checks to compare
- Map actual dependencies. Compare what this check establishes with the other devices in the path.
- Correlate failure and recovery. Compare what this check establishes with the other devices in the path.
- Evaluate a staged improvement. Compare what this check establishes with the other devices in the path.
Scope matters. Synthetic approved resilience exercise. Test power isolation affects a single rack PDU. No claim is made that application HA can replace physical fault separation.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
Topology and test timestamps demonstrate common-mode loss. Purchasing another logical instance on the same infrastructure would not address the proven risk.
Common mistakes to avoid in this scenario
- More frequent backups remove the outage risk: Increase backup frequency while keeping both running nodes on the same power source.
- The HA software alone guarantees continuity: Accept the design because both appliances report healthy HA status.
A proportionate next action
Prioritise fault-domain separation and a measured failover exercise, alongside capacity and dependency checks.
Limits of the conclusion
This supports the specific risk finding, not a universal architecture prescription. Site, storage and identity dependencies still need separate review.