IBM Support in Iraq After End of Life

IBM End-of-Life Support in Iraq

Iraq’s ICT investment is flowing toward connectivity: fibre backhaul, additional submarine capacity, national data centre capability, and the enterprise cloud uptake that follows them. That is the right priority and the numbers behind it are substantial. It also means something specific for the IBM Power platforms sitting underneath Iraqi banking and oil-sector operations, which is that their replacement is not being funded and is not going to be for some time.

A core system has no natural replacement window

The hardware under a core banking ledger or a process historian is not refreshed on the ordinary cycle, and not because anyone decided that. The application is old and deeply integrated. The institutional knowledge that built it has dispersed. Any migration is a multi-year programme with a failure mode that reaches the front page, competing for funding against projects that add capability rather than preserve it. So the platform stays, and keeps staying, long past the point where IBM has withdrawn support for the generation it runs on.

Withdrawal is not a cliff, it is a slope

Nothing happens on the withdrawal date. The system runs exactly as it did the day before. What changes is the supply position: the entitlement to parts ends, the diagnostic access narrows, and the response commitment expires. On a platform that will not be replaced for years, that gap is not a risk to be accepted for a quarter — it is the operating condition for the foreseeable future, and it deserves a deliberate answer rather than an assumption that nothing will break.

What fails, in order

On a Power estate approaching or past a decade in service, the failure sequence is fairly predictable. Power supplies and fan assemblies go first, because they are mechanical and they have been running continuously. Drives follow. Cache batteries in Storwize control enclosures degrade on their own clock regardless of load. Processor and memory features fail much more rarely — but they are the ones that cannot be improvised, because a POWER8 CDIMM or a specific processor feature is not something an integrator has in a cupboard. Identifying which of those an estate would need, before it needs them, is most of the work.

Feature codes, not model names

Power configurations diverge far more than their model numbers suggest. Two machines both described as S822 can carry different processor features, different memory features and different backplane options, and a part that drops into one will be rejected by the other. Matching by model name produces parts that arrive and cannot be fitted, which on a core system means the outage continues while the correct part is identified. ICD matches by feature code and machine type against the actual configuration, and serial-verifies before dispatch. Browse the IBM server parts catalogue, or the wider Iraq server parts page.